** Description changed: - 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 + [Impact] - Problem is described below: + * reboot(8) command was behaviour different from the documented one, in + particular when passing optional REBOOTCOMMAND argument, whilst not in + runlevel 0 or 6 and without passing --force, shutdown(8) was not invoked + with the appropriate arguments. Actual behaviour was dropping to + runlevel 1, instead of the expected reboot. - When the command "reboot now" is issued: + [Test Case] - root@server:~# reboot now - Broadcast message from root@server - (/dev/pts/0) at 00:00 ... - The system is going down to maintenance mode NOW! + * Whilst booted normally to runlevel 2 after executing: - 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@server:~# reboot - Broadcast message from root@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 + $ sudo reboot please + + * machine should complete reboot.
** Description changed: [Impact] - * reboot(8) command was behaviour different from the documented one, in + * reboot(8) command has behaviour different from the documented one, in particular when passing optional REBOOTCOMMAND argument, whilst not in runlevel 0 or 6 and without passing --force, shutdown(8) was not invoked with the appropriate arguments. Actual behaviour was dropping to runlevel 1, instead of the expected reboot. [Test Case] - * Whilst booted normally to runlevel 2 after executing: + * Whilst booted normally to runlevel 2 after executing: - $ sudo reboot please - - * machine should complete reboot. + $ sudo reboot please + + * machine should complete reboot. ** Summary changed: - 'reboot now' reverting to maintenance mode + 'reboot now' reverting to maintenance mode, instead of rebooting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174272 Title: 'reboot now' reverting to maintenance mode, instead of rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1174272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
