12

in Ubuntu 12.10

user@xyz:~$ sudo initctl --version
initctl (upstart 1.5)
Copyright (C) 2012 Scott James Remnant, Canonical Ltd.

This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
user@xyz:~$ ls -l /etc/init/rs-comm.conf
-rw-r--r-- 1 root root 349 нояб. 15 03:22 /etc/init/rs-comm.conf
user@xyz:~$ sudo initctl reload-configuration
user@xyz:~$ sudo initctl start rs-comm
initctl: Unknown job: rs-comm
pino42
  • 935
xdenser
  • 123

2 Answers2

15

Your job probably contains invalid syntax, which means Upstart will not consider it. Try running the following as a normal user (not as root):

init-checkconf /etc/init/rs-comm.conf
jamesodhunt
  • 849
0

On RedHat v6.8 (and probably other versions and distros) upstart will not see the new job if the filename doesn't have a .conf extension. For example, I just encountered this issue when I created an NGiNX upstart as /etc/init/nginx. initctl list | grep nginx returned nothing. initctl status nginx returned initctl: Unkown job: nginx. So, I renamed the upstart job filename to /etc/init/nginx.conf and it immediately recognized it as a new upstart job. I suspect this could affect a lot of people, so I thought I'd post it as a relevant answer.

dcarrith
  • 141