[Bug 886439] Re: upgrade to upstart 1.3-0ubuntu11 causes unclean shutdown
Clint Byrum
clint at fewbar.com
Mon Dec 12 23:13:04 UTC 2011
Testing confirms that upstart is doing the right thing, this is just a
bug in sysvinit, so closing the upstart task. Fix for the sysvinit issue
is in the merge proposal, and should be uploaded to precise soon after a
bit more testing.
** Changed in: upstart (Ubuntu)
Status: Triaged => 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/886439
Title:
upgrade to upstart 1.3-0ubuntu11 causes unclean shutdown
Status in “sysvinit” package in Ubuntu:
Triaged
Status in “upstart” package in Ubuntu:
Invalid
Bug description:
Steps to reproduce:
1. Start an Ubuntu 11.10 Oneiric instance on EC2.
Example: ec2run ami-bbf539d2 -t t1.micro -k key
2. Save sudo lsof for reference.
3. apt-cache show upstart
The stock version of upstart installed is 1.3-0ubuntu10.
4. sudo apt-get update; sudo apt-get install upstart
upstart is upgraded to 1.3-0ubuntu11
5. Verify that /var/run/init.upgraded is in fact touched by the install.
6. Save sudo lsof for reference.
7. sudo shutdown -h now
The console displays while unmounting:
mount: / is busy
This causes filesystem recovery errors on next boot.
The post-upgrade lsof is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/886439/+subscriptions
More information about the foundations-bugs
mailing list