{"id":2250,"date":"2022-10-06T19:47:44","date_gmt":"2022-10-06T17:47:44","guid":{"rendered":"https:\/\/nguenkam.com\/blog\/?p=2250"},"modified":"2022-10-12T01:00:43","modified_gmt":"2022-10-11T23:00:43","slug":"fixes-system-has-not-been-booted-with-systemd-as-init-system","status":"publish","type":"post","link":"https:\/\/nguenkam.com\/blog\/index.php\/2022\/10\/06\/fixes-system-has-not-been-booted-with-systemd-as-init-system\/","title":{"rendered":"[ Fixes] System Has Not Been Booted With Systemd as Init System"},"content":{"rendered":"\n

When you run Systemd commands, you may receive error “System has not been booted with systemd as init system (PID 1). Can’t operate.<\/strong><\/p>\n\n\n\n

The reason why this error occurs is that the Linux system is not using systemd as the init system : you are trying to use systemd command to manage services<\/a> on Linux but your system doesn’t use systemd<\/a> and (most likely) using the classic SysV init<\/a> (sysvinit) system.<\/em><\/p>\n\n\n\n

But how is that possible? If you are using Ubuntu inside Windows using WSL, you will have SysV<\/strong> instead of systemd<\/strong> and your system will complain when you run the systemctl command (intended for Linux systems with systemd init system).<\/em><\/p>\n\n\n\n

<\/div>\n\n\n\n
How to know which “Init System” you are using ?<\/h5>\n\n\n\n

You may use this command to know the process name associated with PID 1 (the first process that runs on your system):<\/p>\n\n\n\n

ps -p 1 -o comm=<\/code><\/pre>\n\n\n\n
It should show init or sysv (or something like that) in the output. If you see init, your system is not using systemd and you should use the init commands as explained in the next section.<\/p>\n\n\n\n
<\/div>\n\n\n\n
How to fix ‘System has not been booted with systemd’ error?<\/h5>\n\n\n\n
The simple answer is to not use the systemctl command. Instead, use the equivalent sysvinit command.<\/p>\n\n\n\n
It’s not too complicated and both commands have somewhat similar syntax.<\/p>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n
<\/h5>\n","protected":false},"excerpt":{"rendered":"
When you run Systemd commands, you may receive error “System has not been booted with systemd as init system (PID 1). Can’t operate. The reason why this error occurs is that the Linux system is not using systemd as the init system : you are trying to use systemd command to manage services on Linux but your […]<\/p>\n","protected":false},"author":1,"featured_media":2276,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[172,171,193,608,605,225,227,606,607,161,217,580],"_links":{"self":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2250"}],"collection":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=2250"}],"version-history":[{"count":4,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2250\/revisions"}],"predecessor-version":[{"id":2256,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2250\/revisions\/2256"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/media\/2276"}],"wp:attachment":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2250"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2250"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2250"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}