How to resolve 'System has not been booted with systemd as init system (PID 1). Can't operate'

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite
1












When I use this command:



root:~# systemctl


Output is:



System has not been booted with systemd as init system (PID 1). Can't operate


This problem occurred in "Kali Linux" and "Debian 9"
How can I resolve this problem?







share|improve this question















  • 1




    That means that the system is running with sysvinit rather than systemd. What are you trying to do? I.e., what do you need to use systemctl for?
    – Stephen Kitt
    Apr 27 at 9:20










  • @StephenKitt I would like to start any package with systemctl, like: systectl openvas start
    – Red Science
    Apr 27 at 12:16











  • OK, but why specifically with systemctl?
    – Stephen Kitt
    Apr 27 at 12:20














up vote
2
down vote

favorite
1












When I use this command:



root:~# systemctl


Output is:



System has not been booted with systemd as init system (PID 1). Can't operate


This problem occurred in "Kali Linux" and "Debian 9"
How can I resolve this problem?







share|improve this question















  • 1




    That means that the system is running with sysvinit rather than systemd. What are you trying to do? I.e., what do you need to use systemctl for?
    – Stephen Kitt
    Apr 27 at 9:20










  • @StephenKitt I would like to start any package with systemctl, like: systectl openvas start
    – Red Science
    Apr 27 at 12:16











  • OK, but why specifically with systemctl?
    – Stephen Kitt
    Apr 27 at 12:20












up vote
2
down vote

favorite
1









up vote
2
down vote

favorite
1






1





When I use this command:



root:~# systemctl


Output is:



System has not been booted with systemd as init system (PID 1). Can't operate


This problem occurred in "Kali Linux" and "Debian 9"
How can I resolve this problem?







share|improve this question











When I use this command:



root:~# systemctl


Output is:



System has not been booted with systemd as init system (PID 1). Can't operate


This problem occurred in "Kali Linux" and "Debian 9"
How can I resolve this problem?









share|improve this question










share|improve this question




share|improve this question









asked Apr 27 at 8:50









Red Science

1616




1616







  • 1




    That means that the system is running with sysvinit rather than systemd. What are you trying to do? I.e., what do you need to use systemctl for?
    – Stephen Kitt
    Apr 27 at 9:20










  • @StephenKitt I would like to start any package with systemctl, like: systectl openvas start
    – Red Science
    Apr 27 at 12:16











  • OK, but why specifically with systemctl?
    – Stephen Kitt
    Apr 27 at 12:20












  • 1




    That means that the system is running with sysvinit rather than systemd. What are you trying to do? I.e., what do you need to use systemctl for?
    – Stephen Kitt
    Apr 27 at 9:20










  • @StephenKitt I would like to start any package with systemctl, like: systectl openvas start
    – Red Science
    Apr 27 at 12:16











  • OK, but why specifically with systemctl?
    – Stephen Kitt
    Apr 27 at 12:20







1




1




That means that the system is running with sysvinit rather than systemd. What are you trying to do? I.e., what do you need to use systemctl for?
– Stephen Kitt
Apr 27 at 9:20




That means that the system is running with sysvinit rather than systemd. What are you trying to do? I.e., what do you need to use systemctl for?
– Stephen Kitt
Apr 27 at 9:20












@StephenKitt I would like to start any package with systemctl, like: systectl openvas start
– Red Science
Apr 27 at 12:16





@StephenKitt I would like to start any package with systemctl, like: systectl openvas start
– Red Science
Apr 27 at 12:16













OK, but why specifically with systemctl?
– Stephen Kitt
Apr 27 at 12:20




OK, but why specifically with systemctl?
– Stephen Kitt
Apr 27 at 12:20










1 Answer
1






active

oldest

votes

















up vote
1
down vote













To start and stop services without having to worry about which init system is in use, you should use service:



service openvas start


will use whatever command is appropriate to start the openvas service.






share|improve this answer





















  • no, output is root:~# service openvas start Unknown operation openvas.
    – Red Science
    Apr 27 at 12:26










  • That means that there is no openvas service (no /etc/init.d/openvas in your case). Is there?
    – Stephen Kitt
    Apr 27 at 12:41










  • no, this program is not over there, I should ln -s? if it is true, How can I use it exactly for every program? if it is not true, What can I do?
    – Red Science
    Apr 27 at 20:20











  • Unfortunately it’s not as simple as that, you can’t turn a program into a service by linking it in /etc/init.d. You need to write (or find) an init script for OpenVAS, or a systemd unit (and switch to systemd).
    – Stephen Kitt
    Apr 27 at 20:42










  • In Ubuntu, I see another error message for systemctl command output: Failed to connect to bus: No such file or directory, What is the meaning of this message?
    – Red Science
    Apr 27 at 21:37










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440364%2fhow-to-resolve-system-has-not-been-booted-with-systemd-as-init-system-pid-1%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote













To start and stop services without having to worry about which init system is in use, you should use service:



service openvas start


will use whatever command is appropriate to start the openvas service.






share|improve this answer





















  • no, output is root:~# service openvas start Unknown operation openvas.
    – Red Science
    Apr 27 at 12:26










  • That means that there is no openvas service (no /etc/init.d/openvas in your case). Is there?
    – Stephen Kitt
    Apr 27 at 12:41










  • no, this program is not over there, I should ln -s? if it is true, How can I use it exactly for every program? if it is not true, What can I do?
    – Red Science
    Apr 27 at 20:20











  • Unfortunately it’s not as simple as that, you can’t turn a program into a service by linking it in /etc/init.d. You need to write (or find) an init script for OpenVAS, or a systemd unit (and switch to systemd).
    – Stephen Kitt
    Apr 27 at 20:42










  • In Ubuntu, I see another error message for systemctl command output: Failed to connect to bus: No such file or directory, What is the meaning of this message?
    – Red Science
    Apr 27 at 21:37














up vote
1
down vote













To start and stop services without having to worry about which init system is in use, you should use service:



service openvas start


will use whatever command is appropriate to start the openvas service.






share|improve this answer





















  • no, output is root:~# service openvas start Unknown operation openvas.
    – Red Science
    Apr 27 at 12:26










  • That means that there is no openvas service (no /etc/init.d/openvas in your case). Is there?
    – Stephen Kitt
    Apr 27 at 12:41










  • no, this program is not over there, I should ln -s? if it is true, How can I use it exactly for every program? if it is not true, What can I do?
    – Red Science
    Apr 27 at 20:20











  • Unfortunately it’s not as simple as that, you can’t turn a program into a service by linking it in /etc/init.d. You need to write (or find) an init script for OpenVAS, or a systemd unit (and switch to systemd).
    – Stephen Kitt
    Apr 27 at 20:42










  • In Ubuntu, I see another error message for systemctl command output: Failed to connect to bus: No such file or directory, What is the meaning of this message?
    – Red Science
    Apr 27 at 21:37












up vote
1
down vote










up vote
1
down vote









To start and stop services without having to worry about which init system is in use, you should use service:



service openvas start


will use whatever command is appropriate to start the openvas service.






share|improve this answer













To start and stop services without having to worry about which init system is in use, you should use service:



service openvas start


will use whatever command is appropriate to start the openvas service.







share|improve this answer













share|improve this answer



share|improve this answer











answered Apr 27 at 12:23









Stephen Kitt

140k22302363




140k22302363











  • no, output is root:~# service openvas start Unknown operation openvas.
    – Red Science
    Apr 27 at 12:26










  • That means that there is no openvas service (no /etc/init.d/openvas in your case). Is there?
    – Stephen Kitt
    Apr 27 at 12:41










  • no, this program is not over there, I should ln -s? if it is true, How can I use it exactly for every program? if it is not true, What can I do?
    – Red Science
    Apr 27 at 20:20











  • Unfortunately it’s not as simple as that, you can’t turn a program into a service by linking it in /etc/init.d. You need to write (or find) an init script for OpenVAS, or a systemd unit (and switch to systemd).
    – Stephen Kitt
    Apr 27 at 20:42










  • In Ubuntu, I see another error message for systemctl command output: Failed to connect to bus: No such file or directory, What is the meaning of this message?
    – Red Science
    Apr 27 at 21:37
















  • no, output is root:~# service openvas start Unknown operation openvas.
    – Red Science
    Apr 27 at 12:26










  • That means that there is no openvas service (no /etc/init.d/openvas in your case). Is there?
    – Stephen Kitt
    Apr 27 at 12:41










  • no, this program is not over there, I should ln -s? if it is true, How can I use it exactly for every program? if it is not true, What can I do?
    – Red Science
    Apr 27 at 20:20











  • Unfortunately it’s not as simple as that, you can’t turn a program into a service by linking it in /etc/init.d. You need to write (or find) an init script for OpenVAS, or a systemd unit (and switch to systemd).
    – Stephen Kitt
    Apr 27 at 20:42










  • In Ubuntu, I see another error message for systemctl command output: Failed to connect to bus: No such file or directory, What is the meaning of this message?
    – Red Science
    Apr 27 at 21:37















no, output is root:~# service openvas start Unknown operation openvas.
– Red Science
Apr 27 at 12:26




no, output is root:~# service openvas start Unknown operation openvas.
– Red Science
Apr 27 at 12:26












That means that there is no openvas service (no /etc/init.d/openvas in your case). Is there?
– Stephen Kitt
Apr 27 at 12:41




That means that there is no openvas service (no /etc/init.d/openvas in your case). Is there?
– Stephen Kitt
Apr 27 at 12:41












no, this program is not over there, I should ln -s? if it is true, How can I use it exactly for every program? if it is not true, What can I do?
– Red Science
Apr 27 at 20:20





no, this program is not over there, I should ln -s? if it is true, How can I use it exactly for every program? if it is not true, What can I do?
– Red Science
Apr 27 at 20:20













Unfortunately it’s not as simple as that, you can’t turn a program into a service by linking it in /etc/init.d. You need to write (or find) an init script for OpenVAS, or a systemd unit (and switch to systemd).
– Stephen Kitt
Apr 27 at 20:42




Unfortunately it’s not as simple as that, you can’t turn a program into a service by linking it in /etc/init.d. You need to write (or find) an init script for OpenVAS, or a systemd unit (and switch to systemd).
– Stephen Kitt
Apr 27 at 20:42












In Ubuntu, I see another error message for systemctl command output: Failed to connect to bus: No such file or directory, What is the meaning of this message?
– Red Science
Apr 27 at 21:37




In Ubuntu, I see another error message for systemctl command output: Failed to connect to bus: No such file or directory, What is the meaning of this message?
– Red Science
Apr 27 at 21:37












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440364%2fhow-to-resolve-system-has-not-been-booted-with-systemd-as-init-system-pid-1%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay