Suddenly, shutdown command can't be found anymore The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!Debian package installation problems - Bus errors, dpkg post-installation exit status 135Anyone else experiencing high rates of Linux server crashes during a leap second day?Can't install anymore MySQL on debian after deletion of various foldersUbuntu samba/raid server shutdown failsMySQL from Deb changing configuration after installing perl packages?removed files from /tmp/ directory - can't login anymoreapt-get dist-upgrade wants to install x11 on a router?docker.io package reports missing only on EC2debian wheezy requiring libc6 >= 2.14Sending graceful shutdown via AMT to intel NUC
Did God make two great lights or did He make the great light two?
Do warforged have souls?
What can I do if neighbor is blocking my solar panels intentionally?
How to delete random line from file using Unix command?
Semisimplicity of the category of coherent sheaves?
Are spiders unable to hurt humans, especially very small spiders?
What aspect of planet Earth must be changed to prevent the industrial revolution?
First use of “packing” as in carrying a gun
What information about me do stores get via my credit card?
Did the new image of black hole confirm the general theory of relativity?
Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?
Python - Fishing Simulator
How to prevent selfdestruct from another contract
Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?
When did F become S? Why?
Derivation tree not rendering
how can a perfect fourth interval be considered either consonant or dissonant?
How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time
How did passengers keep warm on sail ships?
How are presidential pardons supposed to be used?
Simulating Exploding Dice
Empty set is subset of every set? If yes, why that...
Working through the single responsibility principle (SRP) in Python when calls are expensive
Why can't devices on different VLANs, but on the same subnet, communicate?
Suddenly, shutdown command can't be found anymore
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Debian package installation problems - Bus errors, dpkg post-installation exit status 135Anyone else experiencing high rates of Linux server crashes during a leap second day?Can't install anymore MySQL on debian after deletion of various foldersUbuntu samba/raid server shutdown failsMySQL from Deb changing configuration after installing perl packages?removed files from /tmp/ directory - can't login anymoreapt-get dist-upgrade wants to install x11 on a router?docker.io package reports missing only on EC2debian wheezy requiring libc6 >= 2.14Sending graceful shutdown via AMT to intel NUC
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I logged in to my Debian 7 server, did an upgrade using apt and wanted to shutdown+reboot using shutdown -r now as i did a lot of times before. This time, the shutdown command can't be found anymore. I've already read somewhere that i can try it with the whole path /sbin/shutdown, but the programm isn't there, too. I also can't find the reboot command anywhere.
What went wrong? What can i do to restore the shutdown command?
debian debian-wheezy shutdown
asked Oct 31 '14 at 14:58
TheJeedTheJeed
12117
add a comment |
I logged in to my Debian 7 server, did an upgrade using apt and wanted to shutdown+reboot using shutdown -r now as i did a lot of times before. This time, the shutdown command can't be found anymore. I've already read somewhere that i can try it with the whole path /sbin/shutdown, but the programm isn't there, too. I also can't find the reboot command anywhere.
What went wrong? What can i do to restore the shutdown command?
debian debian-wheezy shutdown
asked Oct 31 '14 at 14:58
TheJeedTheJeed
12117
add a comment |
I logged in to my Debian 7 server, did an upgrade using apt and wanted to shutdown+reboot using shutdown -r now as i did a lot of times before. This time, the shutdown command can't be found anymore. I've already read somewhere that i can try it with the whole path /sbin/shutdown, but the programm isn't there, too. I also can't find the reboot command anywhere.
What went wrong? What can i do to restore the shutdown command?
debian debian-wheezy shutdown
asked Oct 31 '14 at 14:58
TheJeedTheJeed
12117
I logged in to my Debian 7 server, did an upgrade using apt and wanted to shutdown+reboot using shutdown -r now as i did a lot of times before. This time, the shutdown command can't be found anymore. I've already read somewhere that i can try it with the whole path /sbin/shutdown, but the programm isn't there, too. I also can't find the reboot command anywhere.
What went wrong? What can i do to restore the shutdown command?
debian debian-wheezy shutdown
debian debian-wheezy shutdown
asked Oct 31 '14 at 14:58
TheJeedTheJeed
12117
asked Oct 31 '14 at 14:58
TheJeedTheJeed
12117
asked Oct 31 '14 at 14:58
TheJeedTheJeed
12117
asked Oct 31 '14 at 14:58
TheJeedTheJeed
12117
asked Oct 31 '14 at 14:58
TheJeedTheJeed
12117
12117
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
$ dpkg -S /sbin/shutdown
sysvinit-core: /sbin/shutdown
You probably "upgraded" to systemd, removing shutdown and friends. If so, you now need to do systemctl poweroff to shutdown the system. Why does systemd not provide an alias to shutdown? Why not indeed...
EDIT:
/sbin/shutdown should be available if you install the systemd-sysv package. It would be nice if systemd would recommend or even just suggest systemd-sysv.
answered Oct 31 '14 at 15:07
wurtelwurtel
2,923512
You were right! I reinstalled systemd and I've got my shutdown command back where it belongs. Thanks a lot!
– TheJeed
Oct 31 '14 at 15:11
systemd breaking habits :(
– Hrvoje Špoljar
Oct 31 '14 at 15:12
@wurtel As can be seen here the file/sbin/shutdownexists insysvinit,systemd-sysvandupstartin Debian Wheezy.
– Håkan Lindqvist
Oct 31 '14 at 15:13
1
Ah, I apologize, I did search packages.debian.org first, but I think I was mentally grepping forsomething-systemd, notsystemd-something. I'll edit my answer to reflect that.
– wurtel
Oct 31 '14 at 15:47
add a comment |
I found this post after an apt-get dist-upgrade from Debian stretch to Debian buster left me with no shutdown or reboot commands. I tried apt-get install systemd-sysv as suggested above and discovered it was already present.
I was surprised to find that somehow my PATH had gotten mucked up and no longer
included /sbin. So /sbin/reboot worked just fine.
I answer here in case other folks run into this situation after an upgrade and become superstitious. The lack of similar concerns on the net suggests this is a rare occurrence. It is obvious that one should check one's path before concluding a command is missing. OTOH, I did a which reboot and got nothing. My goto tool failed me and so I missed the obvious.
answered Oct 13 '18 at 22:32
Richard SonnenfeldRichard Sonnenfeld
311
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f641165%2fsuddenly-shutdown-command-cant-be-found-anymore%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
$ dpkg -S /sbin/shutdown
sysvinit-core: /sbin/shutdown
You probably "upgraded" to systemd, removing shutdown and friends. If so, you now need to do systemctl poweroff to shutdown the system. Why does systemd not provide an alias to shutdown? Why not indeed...
EDIT:
/sbin/shutdown should be available if you install the systemd-sysv package. It would be nice if systemd would recommend or even just suggest systemd-sysv.
answered Oct 31 '14 at 15:07
wurtelwurtel
2,923512
You were right! I reinstalled systemd and I've got my shutdown command back where it belongs. Thanks a lot!
– TheJeed
Oct 31 '14 at 15:11
systemd breaking habits :(
– Hrvoje Špoljar
Oct 31 '14 at 15:12
@wurtel As can be seen here the file/sbin/shutdownexists insysvinit,systemd-sysvandupstartin Debian Wheezy.
– Håkan Lindqvist
Oct 31 '14 at 15:13
1
Ah, I apologize, I did search packages.debian.org first, but I think I was mentally grepping forsomething-systemd, notsystemd-something. I'll edit my answer to reflect that.
– wurtel
Oct 31 '14 at 15:47
add a comment |
$ dpkg -S /sbin/shutdown
sysvinit-core: /sbin/shutdown
You probably "upgraded" to systemd, removing shutdown and friends. If so, you now need to do systemctl poweroff to shutdown the system. Why does systemd not provide an alias to shutdown? Why not indeed...
EDIT:
/sbin/shutdown should be available if you install the systemd-sysv package. It would be nice if systemd would recommend or even just suggest systemd-sysv.
answered Oct 31 '14 at 15:07
wurtelwurtel
2,923512
You were right! I reinstalled systemd and I've got my shutdown command back where it belongs. Thanks a lot!
– TheJeed
Oct 31 '14 at 15:11
systemd breaking habits :(
– Hrvoje Špoljar
Oct 31 '14 at 15:12
@wurtel As can be seen here the file/sbin/shutdownexists insysvinit,systemd-sysvandupstartin Debian Wheezy.
– Håkan Lindqvist
Oct 31 '14 at 15:13
1
Ah, I apologize, I did search packages.debian.org first, but I think I was mentally grepping forsomething-systemd, notsystemd-something. I'll edit my answer to reflect that.
– wurtel
Oct 31 '14 at 15:47
add a comment |
$ dpkg -S /sbin/shutdown
sysvinit-core: /sbin/shutdown
You probably "upgraded" to systemd, removing shutdown and friends. If so, you now need to do systemctl poweroff to shutdown the system. Why does systemd not provide an alias to shutdown? Why not indeed...
EDIT:
/sbin/shutdown should be available if you install the systemd-sysv package. It would be nice if systemd would recommend or even just suggest systemd-sysv.
answered Oct 31 '14 at 15:07
wurtelwurtel
2,923512
$ dpkg -S /sbin/shutdown
sysvinit-core: /sbin/shutdown
You probably "upgraded" to systemd, removing shutdown and friends. If so, you now need to do systemctl poweroff to shutdown the system. Why does systemd not provide an alias to shutdown? Why not indeed...
EDIT:
/sbin/shutdown should be available if you install the systemd-sysv package. It would be nice if systemd would recommend or even just suggest systemd-sysv.
answered Oct 31 '14 at 15:07
wurtelwurtel
2,923512
edited Oct 31 '14 at 15:50
answered Oct 31 '14 at 15:07
wurtelwurtel
2,923512
answered Oct 31 '14 at 15:07
wurtelwurtel
2,923512
answered Oct 31 '14 at 15:07
wurtelwurtel
2,923512
2,923512
You were right! I reinstalled systemd and I've got my shutdown command back where it belongs. Thanks a lot!
– TheJeed
Oct 31 '14 at 15:11
systemd breaking habits :(
– Hrvoje Špoljar
Oct 31 '14 at 15:12
@wurtel As can be seen here the file/sbin/shutdownexists insysvinit,systemd-sysvandupstartin Debian Wheezy.
– Håkan Lindqvist
Oct 31 '14 at 15:13
1
Ah, I apologize, I did search packages.debian.org first, but I think I was mentally grepping forsomething-systemd, notsystemd-something. I'll edit my answer to reflect that.
– wurtel
Oct 31 '14 at 15:47
add a comment |
You were right! I reinstalled systemd and I've got my shutdown command back where it belongs. Thanks a lot!
– TheJeed
Oct 31 '14 at 15:11
systemd breaking habits :(
– Hrvoje Špoljar
Oct 31 '14 at 15:12
@wurtel As can be seen here the file/sbin/shutdownexists insysvinit,systemd-sysvandupstartin Debian Wheezy.
– Håkan Lindqvist
Oct 31 '14 at 15:13
1
Ah, I apologize, I did search packages.debian.org first, but I think I was mentally grepping forsomething-systemd, notsystemd-something. I'll edit my answer to reflect that.
– wurtel
Oct 31 '14 at 15:47
You were right! I reinstalled systemd and I've got my shutdown command back where it belongs. Thanks a lot!
– TheJeed
Oct 31 '14 at 15:11
You were right! I reinstalled systemd and I've got my shutdown command back where it belongs. Thanks a lot!
– TheJeed
Oct 31 '14 at 15:11
systemd breaking habits :(
– Hrvoje Špoljar
Oct 31 '14 at 15:12
systemd breaking habits :(
– Hrvoje Špoljar
Oct 31 '14 at 15:12
@wurtel As can be seen here the file
/sbin/shutdown exists in sysvinit, systemd-sysv and upstart in Debian Wheezy.– Håkan Lindqvist
Oct 31 '14 at 15:13
@wurtel As can be seen here the file
/sbin/shutdown exists in sysvinit, systemd-sysv and upstart in Debian Wheezy.– Håkan Lindqvist
Oct 31 '14 at 15:13
1
1
Ah, I apologize, I did search packages.debian.org first, but I think I was mentally grepping for
something-systemd, not systemd-something. I'll edit my answer to reflect that.– wurtel
Oct 31 '14 at 15:47
Ah, I apologize, I did search packages.debian.org first, but I think I was mentally grepping for
something-systemd, not systemd-something. I'll edit my answer to reflect that.– wurtel
Oct 31 '14 at 15:47
add a comment |
I found this post after an apt-get dist-upgrade from Debian stretch to Debian buster left me with no shutdown or reboot commands. I tried apt-get install systemd-sysv as suggested above and discovered it was already present.
I was surprised to find that somehow my PATH had gotten mucked up and no longer
included /sbin. So /sbin/reboot worked just fine.
I answer here in case other folks run into this situation after an upgrade and become superstitious. The lack of similar concerns on the net suggests this is a rare occurrence. It is obvious that one should check one's path before concluding a command is missing. OTOH, I did a which reboot and got nothing. My goto tool failed me and so I missed the obvious.
answered Oct 13 '18 at 22:32
Richard SonnenfeldRichard Sonnenfeld
311
add a comment |
I found this post after an apt-get dist-upgrade from Debian stretch to Debian buster left me with no shutdown or reboot commands. I tried apt-get install systemd-sysv as suggested above and discovered it was already present.
I was surprised to find that somehow my PATH had gotten mucked up and no longer
included /sbin. So /sbin/reboot worked just fine.
I answer here in case other folks run into this situation after an upgrade and become superstitious. The lack of similar concerns on the net suggests this is a rare occurrence. It is obvious that one should check one's path before concluding a command is missing. OTOH, I did a which reboot and got nothing. My goto tool failed me and so I missed the obvious.
answered Oct 13 '18 at 22:32
Richard SonnenfeldRichard Sonnenfeld
311
add a comment |
I found this post after an apt-get dist-upgrade from Debian stretch to Debian buster left me with no shutdown or reboot commands. I tried apt-get install systemd-sysv as suggested above and discovered it was already present.
I was surprised to find that somehow my PATH had gotten mucked up and no longer
included /sbin. So /sbin/reboot worked just fine.
I answer here in case other folks run into this situation after an upgrade and become superstitious. The lack of similar concerns on the net suggests this is a rare occurrence. It is obvious that one should check one's path before concluding a command is missing. OTOH, I did a which reboot and got nothing. My goto tool failed me and so I missed the obvious.
answered Oct 13 '18 at 22:32
Richard SonnenfeldRichard Sonnenfeld
311
I found this post after an apt-get dist-upgrade from Debian stretch to Debian buster left me with no shutdown or reboot commands. I tried apt-get install systemd-sysv as suggested above and discovered it was already present.
I was surprised to find that somehow my PATH had gotten mucked up and no longer
included /sbin. So /sbin/reboot worked just fine.
I answer here in case other folks run into this situation after an upgrade and become superstitious. The lack of similar concerns on the net suggests this is a rare occurrence. It is obvious that one should check one's path before concluding a command is missing. OTOH, I did a which reboot and got nothing. My goto tool failed me and so I missed the obvious.
answered Oct 13 '18 at 22:32
Richard SonnenfeldRichard Sonnenfeld
311
answered Oct 13 '18 at 22:32
Richard SonnenfeldRichard Sonnenfeld
311
answered Oct 13 '18 at 22:32
Richard SonnenfeldRichard Sonnenfeld
311
answered Oct 13 '18 at 22:32
Richard SonnenfeldRichard Sonnenfeld
311
311
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f641165%2fsuddenly-shutdown-command-cant-be-found-anymore%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
