Ubuntu – Correct way to install a custom upstart service

upstart

I am using upstart for services on my servers. Writing a conf file and placing it in /etc/init is easy enough, but that doesn't seem to completely install. For one, the service --status-all doesn't list my new service. I checked and if I make a link in /etc/init.d to /lib/init/ubstart-job it'll show up in the status. But doing this manually makes me think I'm not doing it right, and there may well be other configuration steps which aren't being done.

What is the correct way to install an upstart service such that it is properly registered in all tools dealing with services?

Best Answer

When you initially copy a new conf file into the /etc/init folder you need to call:

initctl reload-configuration

By this your upstart should be properly registered.

Related Solutions

Ubuntu – Why isn’t the upstart service starting on system boot

I would recommend increasing the verbosity of the job, e.g. by using pre-start/post-start entries.

pre-start script
  logger "pre-start for myprog"
end script

post-start script
  logger "post-start for myprog"
end script

# and for PMS itself:
script
  logger "just before executing PMS"
  exec /home/administrator/pms-current/PMS.sh
end script

Further information at http://upstart.ubuntu.com/cookbook/

Also have a look at http://upstart.ubuntu.com/wiki/Debugging

Ubuntu – How to diagnose Upstart errors

Try:

/var/log/upstart/JOBNAME.log

You may want to consider converting it to a task while you debug it.

start on spatial-start

task

exec /spatial/server_init.sh

then from the console:

initctl emit spatial-start
initctl status spatial-start

Best Answer

Related Solutions

Ubuntu – Why isn’t the upstart service starting on system boot

Ubuntu – How to diagnose Upstart errors

Related Question