How to use systemd instead upstart?

Question

Suddenly systemctl stopped to work while I ssh'ed in my remote server to check service status. Output was

Failed to list units: Launch helper exited with unknown return code 1

I discovered that now upstart is used (after a couple of reboots trying to make systemctl work).

Can I use systemd as my main init again? I didn't found any info how to switch from upstart to systemd here.

Ubuntu 16.04.5.

@GunnarHjalmarsson hmm, have'nt until now. Can I upgrade without breaking my webservers and so on? I found this question so far — Tarasovych, May 09 '19 at 12:21
Don't know what version of Ubuntu your using but did you see this on that link you provided? First, it is important to note that systemd is only fully supported in Ubuntu 15.04 and later releases. While systemd is available in prior releases through the Ubuntu repositories, there is a deemphasis of support for these releases as noted here. Hence, it is advised to use the default upstart on prior releases. — George Udosen, May 09 '19 at 12:26
@Tarasovych: Nobody can guarantee that you won't need to tweak a thing or two to adapt to updated software. The upside is that you get an Ubuntu version which lasts until 2023 instead of 2021, and systemd is there by default. — Gunnar Hjalmarsson, May 09 '19 at 12:27
@GeorgeUdosen "Don't know what version of Ubuntu your using" - last line of my question :) — Tarasovych, May 09 '19 at 12:27
See this https://serverfault.com/a/778202/369307, but of course a backup is need! — George Udosen, May 09 '19 at 12:37

score 0 · Answer 1 · answered May 09 '19 at 12:47

0

Thanks to George Udosen, I found this article.

I edited /etc/default/grub - added init=/bin/systemd to GRUB_CMDLINE_LINUX_DEFAULT, than restarted the server sudo shutdown -r now

answered May 09 '19 at 12:47

Tarasovych

1 Answers1