EC2 linux any and all upstart jobs returning "unrecognised service"

Question

Having a nightmare migrating some upstart jobs from Ubuntu to EC2 Linux (ElasticBeanstalk)

I am unable to get even the most basic task to work. I am using the script below which works perfectly on Ubuntu but returns the very unhelpful "unrecognised service" when I try to start it in EC2 Linux. I have read this is usually a syntax error but that doesnt follow if this is syntactically OK for Ubuntu. Any help massively appreciated, I just need any working example.

This is in /etc/init/test.conf created as root user.

Console:

# sudo service test start
# test: unrecognized service

/etc/init/test.conf:

description "test"

start on startup

script
  echo $(ping -c 1 serverfault.com) > /var/log/testjob.log
end script

score 12 · Accepted Answer · edited May 05 '16 at 01:03

12

So for some reason initctl likes it and service doesnt...

sudo initctl start test
test start/running, process 8776

A bug in EC2 Linux me thinks. My example exactly conforms to the documentation but no biggy to switch to using initctl

If you like to check which services are running you also can do this:

sudo initctl list

And to verify where the log error read the file in /var/log/messages

edited May 05 '16 at 01:03

Bill Weiss

10,782
3
37
65

answered Dec 30 '14 at 13:44

Mike Miller

401
1
3
9

Maybe I should have searched for this answer before spending a day trying to fix it myself, and then trying to install daemontools........ – Asfand Qazi Dec 23 '15 at 12:12

score 1 · Answer 2 · answered Dec 30 '14 at 12:44

1

If you are using the AWS Linux AMI instead of the Ubuntu one use:

start on started network

answered Dec 30 '14 at 12:44

Optichip

357
1
7

Appreciate the suggestion but no joy. Still giving me the "unrecognised service" error – Mike Miller Dec 30 '14 at 12:54
what AMI are you using? – Optichip Dec 30 '14 at 13:01
Latest EC2 Linux - whatever Amazon spin up with ElasticBeanstalk applications. Thanks for your help, found an answer posted below – Mike Miller Dec 30 '14 at 13:42
Great, I'll keep that one in mind as well. – Optichip Dec 30 '14 at 13:54
Further to your suggestion I think the elasticbeanstalk equivalent would be `start on started elastic-network-interfaces` – Mike Miller Jan 02 '15 at 10:34
Your suggestion just saved me! I've been running with `start on startup` to no avail all day. – sethetter Sep 15 '17 at 03:21

score 0 · Answer 3 · answered Nov 16 '15 at 20:13

0

With upstart, the syntax should be sudo start test and sudo stop test, rather than the "service" syntax used by the init.d system.

answered Nov 16 '15 at 20:13

grant

188
9

Amazon Linux uses an old version of Upstart, which does not recognise jobs in /etc/init – Asfand Qazi Dec 23 '15 at 12:12

EC2 linux any and all upstart jobs returning "unrecognised service"

3 Answers3