Ubuntu – How to change the order of execution of services at startup

14.04init.dservicesstartup

I have some services in my init.d folder for e.g. hdfs, zookeeper, elasticsearch, hbase and so on.

Now, I have added all those services to startup by doing the update-rc.d 'service' defaults command. As we know, hbase can't run if hdfs and zookeeper are not started. So I want to start hdfs first, then zookeeper and then finally hbase.

how do I do this?

Best Answer

update-rc.d(8) enables or disables services, while the ordering of services is handled by insserv(8), and can be customized by editing the LSB header of the service and setting/adding:

Required-Start: $all

In oldest versions, i can do something like this to determine the order:

update-rc.d myservice start 95 2 3 4 5 . stop 70 0 1 6 .

But after Ubuntu 14, i tried this Ubuntu 16.04 (4.4.0-31-generic):

update-rc.d myservice defaults 95 70

And doesn't work, always creates the order defined in the header:

 sudo find /etc/ -name ???myservice | sort
/etc/rc0.d/K01myservice
/etc/rc1.d/K01myservice
/etc/rc2.d/S03myservice
/etc/rc3.d/S03myservice
/etc/rc4.d/S03myservice
/etc/rc5.d/S03myservice
/etc/rc6.d/K01myservice

Also al try:

update-rc.d myservice defaults any_text_wath_you_want lalala

Ands seems like ignores all the text after "defaults". I don´t know wath it do when my installation order, I do not think that orders previously installed services.

Related Solutions

Ubuntu – Services in rc.d, not starting automatically at boot

I corrected this problem by chuser'ing the files/directories that were involved (including settings). I believe this happened because starting and stopping services with sudo gives them root privileges, whereas they're run as the user account at startup.

Ubuntu – How system services are started in 12.10

Regarding services that are defined in both SysV and upstart, generally if you restart it through SysV you'll see something like this:

al@al-mythtv:~$ sudo /etc/init.d/mysql restart
[sudo] password for al: 
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mysql restart

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) and then start(8) utilities,
e.g. stop mysql ; start mysql. The restart(8) utility is also available.
mysql stop/waiting
mysql start/running, process 29846

What I take this to mean is that Upstart is preferred for these services, and the SysV implementation is just a wrapper.

Also, I think you have the meaning of the directories backwards. /etc/init is upstart configuration, /etc/init.d is the SysV compatibility, but it is just symlinks to upstart for these type of services.

Best Answer

Related Solutions

Ubuntu – Services in rc.d, not starting automatically at boot

Ubuntu – How system services are started in 12.10

Related Question