[Bug 1174272] Re: 'reboot now' reverting to maintenance mode
James Hunt
1174272 at bugs.launchpad.net
Tue May 7 08:50:29 UTC 2013
"shutdown now" is supposed to switch to single-user mode (see bug
1065851).
"reboot now" is invalid - the shutdown command takes a time parameter
(such as "now"), but the reboot command does not (see the man page). By
specifying "reboot now" you are asking the system to reboot by running
the "now" command, which is erroneous.
** Changed in: upstart (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot now' reverting to maintenance mode
Status in “upstart” package in Ubuntu:
Invalid
Bug description:
A forum thread has been opened first, describing the problem. For
reference, that forum thread can be found here:
http://ubuntuforums.org/showthread.php?t=2139160&p=12624806
Problem is described below:
When the command "reboot now" is issued:
root at server:~# reboot now
Broadcast message from root at server
(/dev/pts/0) at 00:00 ...
The system is going down to maintenance mode NOW!
A few moments later.. SSHd is killed, but the box responds to pings
(Inaccessible remotely unless a hard-reset is performed)
* Asking all remaining processes to terminate...
* Killing all remaining processes... [fail]
* Will now switch to single-user mode
Give root password for maintenance
(or type Control-D to continue):
Just "reboot", and it works fine
root at server:~# reboot
Broadcast message from root at server
(/dev/pts/0) at 00:00 ...
The system is going down for reboot NOW!
Some distro's require a time / 'now' as an argument, and thus I became
accustomed to performing my reboots in this way. Now it seems to be a
potential trap that causes the machine not to reboot, which is
especially painful if we're talking about a headless/hosted dedicated
server. Even if ubuntu doesn't like 'reboot now' syntax, I still can't
understand why "reboot now" should bring the box to console
maintenance mode anyway - perhaps it should rather return an error, or
syntax help
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: upstart 1.8-0ubuntu1
Uname: Linux 3.9.0-030900rc8-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
Date: Mon Apr 29 13:22:02 2013
InstallationDate: Installed on 2010-12-11 (870 days ago)
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release i386 (20101007)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_ZA.UTF-8
SHELL=/bin/bash
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.9.0-030900rc8-generic root=UUID=cde38363-cc5e-4b66-ba3d-f64dd0ed4987 ro quiet
SourcePackage: upstart
UpgradeStatus: Upgraded to raring on 2013-04-26 (3 days ago)
UpstartBugCategory: System
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1174272/+subscriptions
More information about the foundations-bugs
mailing list