Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On 12/20/2011 09:47 AM, Clint Byrum wrote: The best way to try and figure out what is causing this is to modify /etc/init.d/umountroot and right before the umount's, add /usr/bin/lsof -n /saved.root.lsof sync This will save a listing of all opened files and which processes have them open. Things marked as 'deleted' in this list are generally the problem. If you see libc6.so opened by upstart, then this bug has regressed. Otherwise, it is probably something else. Thanks. I'll test it later today. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/672177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Excerpts from chtnh's message of Sat Jul 23 04:41:01 UTC 2011: I'm new in Ubuntu (10.10) and in Lauchpad, and I have this bug. I don't understand how you fix it, as there is fix released. Can someone explain me, please? There are other bugs that sometimes cause an unclean shutdown, this one is pretty well understood and fixed. Maybe you have some other services, like mysql, or portmap, that are causing this problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/672177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On 16.02.2011 00:25, Clint Byrum wrote: There are also a couple more bugs covering daemons that need to be shutdown, namely, sshd and portmap. Clint, the portmap Bug #711425 you filed has not got any attention yet, it's still undecided and unassigned - does nobody care? -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Tue, 2011-02-15 at 21:51 +, Paul Crawford wrote: Well it is not yet fixed for 10.04 with the 'proposed' updates. Tonight just rebooted after updates to kernal 2.6.32-29 and guess what? Yes, my syslog contained the following sort of message: Feb 15 21:45:24 paul-ubuntu kernel: [2.341704] EXT4-fs (sda5): 4 orphan inodes deleted So is 'proposed' still part of the 10.04.2 to be released, or will the fix come soon as mentioned for the 10.04.3 CD? Paul, I'm sorry you're still having issues. This is all covered in the previous comments, but to summarize: There is still a pending change to sysvinit to make sure the umounts wait for upstart to re-exec itself. There are also a couple more bugs covering daemons that need to be shutdown, namely, sshd and portmap. 10.04.3 should have all of these fixes, and they should be available soon as updates to 10.04.* as well. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Bad news there: I'm afraid that we've already had to entirely freeze updates for 10.04.2 in order that we can get certification done in time; unfortunately that's a rather time-consuming process and needs a couple of weeks of clearance. I expect that 10.04.3 won't be a problem, though. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
I'm afraid there's no point railing about it here - we're already committed to the date and it would be a colossal rearrangement of many people's schedules to change it at this point. As I say, sorry, and we should be able to get this nailed down for .3. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
At least certified bugs can be documented, with certified workarounds. On Wed, Feb 2, 2011 at 2:05 PM, ingo 672...@bugs.launchpad.net wrote: ... freeze updates for 10.04.2 in order that we can get certification done That means we get certified BUGS - and that 10 months after release! -- You received this bug notification because you are a member of Upstart Developers, which is subscribed to upstart . https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted Status in Upstart: Invalid Status in “eglibc” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: In Progress Status in “upstart” package in Ubuntu: In Progress Status in “eglibc” source package in Lucid: Fix Released Status in “sysvinit” source package in Lucid: In Progress Status in “upstart” source package in Lucid: Fix Released Status in “eglibc” source package in Maverick: Fix Released Status in “sysvinit” source package in Maverick: In Progress Status in “upstart” source package in Maverick: Fix Released Status in “eglibc” source package in Natty: Fix Released Status in “sysvinit” source package in Natty: In Progress Status in “upstart” source package in Natty: In Progress Bug description: On a clean install of Ubuntu 10.04.1, after upgrading the offer libc6 upgrade, on the next reboot the root fs can't be properly unmounted (mount: / is busy). This causes fsck to run on boot and of course some minor issues with the filesystem. This might not be a problem with libc6 itself, but a side effect of upgrading in combination with some other package (I suspect the init process, so I guess upstart). The fsck run, and the orphaned inodes it finds are holding me back from installing this on a new server - especially since this already happens on a clean install of 10.04.1! paul@ubuntu:~$ lsb_release -rd Description: Ubuntu 10.04.1 LTS Release: 10.04 ii libc6 2.11.1-0ubuntu7.2 Embedded GNU C Library: Shared libraries ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libc6 2.11.1-0ubuntu7.2 ProcVersionSignature: Ubuntu 2.6.32-24.39-server 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-server x86_64 Architecture: amd64 Date: Sun Nov 7 16:17:07 2010 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.2) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eglibc -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Sun, 2011-01-23 at 12:39 +, ingo wrote: Observed just another oddity, probably a separate bug in mountall? I tried to mount the / filesystem (ext3) in journal mode to see if this improves the situation by adding the option to /etc/fstab: data=journal,erros=remount-ro But that results in boot process stalling with / filesystem mounted ro and just a console. dmesg | grep -i ext3 tells me: EXT3-fs: mounted filesystem with ordered data mode EXT3-fs (device sda1): Cannot change data mode on remount. The filesystem is mounted in data=ordered mode and you try to remount it in data=journal mode. The only way out and to continue boot-up is to manually remount the fs rw by: mount -o remount,rw /dev/sda1 / and remove the data=journal option from fstab. Ingo, I believe changing the journalling of the root fs in this way is a long standing issue with ext3/ext4, and has nothing to do with the libc6 issue. IIRC, it is only changeable by unmounting the fs, setting it, and then mounting/unmounting again. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Sun, 2011-01-23 at 11:50 +, ingo wrote: Sorry, but I can't reproduce it now, getting still 4 orphaned inodes. Can I insert some lines to log which libs are still in use? Yes, you can put this just after the remounts: lsof -n | grep DEL sleep 10 Which will give you 10 seconds to view anything that still has deleted files open. I recently found that sshd also may interfere w/ the remounting of root in lucid (not as likely in maverick as it is stopped on runlevel [! 2345]) because it is not properly restarted on libc6 upgrade. See bug #531912 for more info on that. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Tue, 2011-02-01 at 16:17 +, ingo wrote: you can put this just after the remounts: lsof -n | grep DEL sleep 10 *Lucid-amd64* I did so (with new libc6 and upstart from Lucid-proposed installed) and found something new: it's the NFS which makes trouble. Portmap and statd are still running! (I just list the essential information here, as I took a screenshot, but could upload the *.png as well.) init: Re-executing /sbin/init mount: / is busy portmap445 daemon DEL REG 8,1 /lib/libnsl-2.11.1.so /lib/libc-2.11.1.so /lib/ld-2.11.1.so rpc.statd 602statdDEL REG 8,1 /lib/libnss_files-2.11.1.so /lib/libnsl-2.11.1.so /lib/libc-2.11.1.so /lib/ld-2.11.1.so Ingo, thanks for the rapid feedback! I think this is actually a new bug against portmap caused by its migration to upstart. /etc/init.d/umountnfs.sh defines # Should-Stop: $network $portmap nfs-common And portmap actually does tell dh_installinit to stop after umountnfs: dh_installinit --name portmap -- start 43 S 2 3 4 5 . start 32 0 6 . stop 81 1 . But there is no way to codify that point in the shutdown into the upstart job, which I suspect is why it has no stop on. I believe the proper way to handle this is to have a matching event to remote-filesystems , unmounted-remote-filesystems, with which to stop on, and then have umountnfs.sh emit that. A more succinct method would be to simply add stop portmap 2/dev/null || : to umountnfs.sh Either way, portmap should be responsible for shutting down at the right moment, and so I've opened bug #711425 against portmap. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Tue, 2011-02-01 at 20:23 +, ingo wrote: But there is no way to codify that point in the shutdown into the upstart job, which I suspect is why it has no stop on. I believe the proper way to handle this is to have a matching event to remote-filesystems , unmounted-remote-filesystems, with which to stop on, and then have umountnfs.sh emit that. Thanks for opening the new bug, Clint. On my machine portmap is started/running anyhow, also if no nfs share has been mounted ever. In Lucid I have just installed 'nfs-common' (not the kernel server!). It is only used when I temporarely mount some nfs3-exports from guests in VBox, or nfs4-exports from my nas (running Lenny-armel). You need to install nfs-common also if you only want just the client - and that brings portmap and rpc.statd. Amaizingly; stopping portmap also stops rpc.statd? Yes, statd stops and starts with portmap... from statd.conf: start on (started portmap ON_BOOT= or (local-filesystems and started portmap ON_BOOT=y)) stop on stopping portmap Another observation: sshd cannot be stopped manually: # /etc/init.d/ssh stop * Stopping OpenBSD Secure Shell server sshd [ OK ] This is bug #531912, which is awaiting review. The init.d script is only retained for chroots. Use 'service ssh stop' until that bug is fixed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Tue, 2011-02-01 at 21:32 +, ingo wrote: Puh, by and by I understand why Ubutu is blamed for use on servers. Do you see any chance to get that mess cleaned up in Lucid? (Squeeze is beeuing released soon) I don't know if I'd call it a mess at this point. The shutdown will certainly be better in 10.04.2 (not quite released but quite frozen) than it was in 10.04 and 10.04.1. I expect it will continue to improve over the next couple of months. Its just an area that didn't receive much testing during the development cycle. The platform as a whole wouldn't be nearly as stable without testers like yourself Ingo, so for that, I thank you. I hope you'll continue to be patient with us and provide feedback as we move forward with more fixes and some re-factoring. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Tue, 2011-02-01 at 23:06 +, Jimmy Merrild Krag wrote: Now (after a while) I've gotten through reading this bug. I have just updated my server, it now runs 10.04.2. Does this mean it has no issues? It's a non-critical server I access remotely. should I care at all, or just wait for things to get even better? So the good news about 10.04.2's shutdown/reboot is that now that upstart can re-exec itself again, further issues should be solvable without rebooting. The bad news is there's quite a few updates that need to be done to protect filesystems on shutdown/reboot: * umountroot needs to wait for init to re-exec itself - addressed in this bug itself, James Hunt is working on that at the moment. * portmap needs to stop after umountnfs - bug #711425 * ssh needs to be restarted on libc6 upgrades - bug #531912 * umountfs needs to wait for all stopping services to stop. bug #616287 On my laptop I see upstart as upgradeable, but the required version of libc6 for that package is not available. Again, should I just wait and see, or do you recommend that I upgrade from proposed? Looks like eglibc went into maverick-proposed on 1/21 but has not been verified yet. See comment #46 from Colin Watson. Looks like the Breaks: field that was added is actually working to keep peoples' systems from.. well.. breaking. :) Jimmy it would be great if you could enable proposed for your laptop and verify that the upgrade works. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
ingo: that's the way the Ubuntu release process works, I'm sorry that this is a surprise to you On Mon, Jan 24, 2011 at 1:00 PM, ingo 672...@bugs.launchpad.net wrote: @Zippo, it is really a sad story with LTS-Lucid. I really don't understand how such a buggy release could pass QC (if there is any?). I.e. today there came in an update of openSSH in Lucid, and still the old bug in the upstart-script '/etc/init/ssh.conf' (stop on runlevel S) is not fixed. Set it to (stop on runlevel [!2345]) - a hint from Clint. In fact Scott has left behind a half done upstart - not only in Lucid. And Clint has taken the ungreatful challenge to clean up the biggest issues. Shutdown process had been neglected to a great part. Unfortunately Canonical is mainly focussing on Natty while Lucid just gets the fixes for the worst. -- You received this bug notification because you are a member of Upstart Developers, which is subscribed to upstart . https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted Status in Upstart: Invalid Status in “eglibc” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: New Status in “upstart” package in Ubuntu: In Progress Status in “eglibc” source package in Lucid: Fix Committed Status in “sysvinit” source package in Lucid: New Status in “upstart” source package in Lucid: Fix Committed Status in “eglibc” source package in Maverick: Fix Committed Status in “sysvinit” source package in Maverick: New Status in “upstart” source package in Maverick: Fix Committed Status in “eglibc” source package in Natty: Fix Released Status in “sysvinit” source package in Natty: New Status in “upstart” source package in Natty: In Progress Bug description: On a clean install of Ubuntu 10.04.1, after upgrading the offer libc6 upgrade, on the next reboot the root fs can't be properly unmounted (mount: / is busy). This causes fsck to run on boot and of course some minor issues with the filesystem. This might not be a problem with libc6 itself, but a side effect of upgrading in combination with some other package (I suspect the init process, so I guess upstart). The fsck run, and the orphaned inodes it finds are holding me back from installing this on a new server - especially since this already happens on a clean install of 10.04.1! paul@ubuntu:~$ lsb_release -rd Description: Ubuntu 10.04.1 LTS Release: 10.04 ii libc6 2.11.1-0ubuntu7.2 Embedded GNU C Library: Shared libraries ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libc6 2.11.1-0ubuntu7.2 ProcVersionSignature: Ubuntu 2.6.32-24.39-server 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-server x86_64 Architecture: amd64 Date: Sun Nov 7 16:17:07 2010 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.2) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eglibc -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Sat, 2011-01-22 at 11:50 +, ingo wrote:
Thanks for Lucid-fix. I did immediately test with new 'libc6' and
'upstart' from Lucid-proposed:
1. just new 'libc6' - does not change anything (8 orphaned inodes after
reboot).
2. + new 'upstart' - gives 1 orphaned inode after reboot.
3. new ('libc6' + 'upstart'), 'apt-get install --reinstall libc6
shutdown -r now' - 4 orphaned inodes.
So it improves the situation definitely, but does not solve it
completely. Did I miss something to update?
No Ingo, you did everything right, I see similar effects.
That is why sysvinit was added to the bug report. The issue is that
while we've restored the ability to tell init to re-exec itself, we have
also introduced a race condition. telinit u exits as soon as it has sent
SIGTERM to pid 1. Almost the very next line in /etc/init.d/umountroot
attempts the remount of / as readonly. If the signal handler doesn't
complete the re-exec before this, then the remount will still fail.
I've been testing a few ways to make telinit or umountroot block until
init re-execs. The important thing is that this way 10.04.2 will ship
with an init that *can* re-exec.
If you add 'sleep 1' after the telinit u line in /etc/init.d/umountroot,
that should give you a much better chance of succeeding the remount.
Hopefully there will be a proper fix available for that early next week,
but I don't know if it will be accepted for 10.04.2 or have to come as
an update to 10.04.2.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because init cannot be
restarted
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Wed, 2011-01-05 at 21:31 +, ingo wrote: Hi Clint, thanks for fast fix - but unfortunately only in Natty which is still in development. This bug was reported for *Lucid*, which in terms of service will even survive Natty. When will that be fixed and who cares? Hi Ingo. This is the normal procedure for stable release updates. If we don't fix it first in the development release, then it will persist into subsequent releases. We need to fix it on the dev version first, and then the fix will be backported to maverick and lucid. I know its hard to remain patient. I'm hoping to get this fix into lucid before 10.04.2 is released in February. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Yes, I know how to drive bzr and dpkg ;-) My point is that if you do that diff, the only occurrence of SIGTERM is in the code for the upstart/udev bridge, that patch doesn't add any handling to upstart itself. Scott On Wed, Dec 29, 2010 at 6:54 AM, Clint Byrum cl...@fewbar.com wrote: On Wed, 2010-12-29 at 00:06 +, Scott James Remnant wrote: Are you sure? I can't find that code at all - it looks like it's been lost somehow quite certain.. its a bit tricky to find it in bzr, but this will give it to you for, say, maverick: $ bzr branch lp:ubuntu/maverick/upstart maverick $ cd maverick $ bzr diff -r tag:upstream-0.6.6..tag:0.6.6-3 apt-get source will wrap it up in the .diff.gz for you as well. -- You received this bug notification because you are a member of Upstart Developers, which is subscribed to upstart . https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted Status in Upstart: Invalid Status in “eglibc” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Confirmed Bug description: On a clean install of Ubuntu 10.04.1, after upgrading the offer libc6 upgrade, on the next reboot the root fs can't be properly unmounted (mount: / is busy). This causes fsck to run on boot and of course some minor issues with the filesystem. This might not be a problem with libc6 itself, but a side effect of upgrading in combination with some other package (I suspect the init process, so I guess upstart). The fsck run, and the orphaned inodes it finds are holding me back from installing this on a new server - especially since this already happens on a clean install of 10.04.1! p...@ubuntu:~$ lsb_release -rd Description: Ubuntu 10.04.1 LTS Release: 10.04 ii libc6 2.11.1-0ubuntu7.2 Embedded GNU C Library: Shared libraries ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libc6 2.11.1-0ubuntu7.2 ProcVersionSignature: Ubuntu 2.6.32-24.39-server 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-server x86_64 Architecture: amd64 Date: Sun Nov 7 16:17:07 2010 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.2) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eglibc -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
I've no idea why that revision got dropped from the Ubuntu package, I did a bit of investigation and it seems to vanish about the point we switched to the auto-importer based packages. My only guess is that bzr undid the cherry-pick as part of a merge. Right, eglibc's postinst should definitely not call telinit u and should touch that upgraded file instead, i thought the code to do that was definitely in glibc's postinst but again I can't find it in the history. It does look very much like we lost a chunk of patches somehow, the bug log shows that they were definitely uploaded! Definitely open bug reports for test failures - these could be signs of bigger problems and shouldn't be overridden to make an upload go through. Scott On Wed, Dec 29, 2010 at 8:17 PM, Clint Byrum cl...@fewbar.com wrote: Some day, I'll learn to pay attention to the details, I promise. Sorry for the confusion. Ok, so I reverse merged r977 back in, which mostly applied cleanly. I then tested this on a natty VM, and, shock, it worked flawlessly. I think we may also need to have eglibc's postinst skip the call to telinit u, and instead touch /var/run/init.upgraded. Its probably open to debate whether we need to flag users to reboot, though I'd prefer that we do. One major problem though, is it seems upstart is FTBFS on natty right now. Without any changes, 0.6.7-3 cannot build, as init/test_conf fails, and utils/test_utmp also fails. Will open a bug report for that post- holiday. I've pushed up a branch, it would be nice if somebody else could test it (I manually disabled test_conf and test_utmp in their respective Makefile.am's and then re-ran automake before building). I will propose the merge after returning from holiday next week. -- You received this bug notification because you are a member of Upstart Developers, which is subscribed to upstart . https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted Status in Upstart: Invalid Status in “eglibc” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Confirmed Bug description: On a clean install of Ubuntu 10.04.1, after upgrading the offer libc6 upgrade, on the next reboot the root fs can't be properly unmounted (mount: / is busy). This causes fsck to run on boot and of course some minor issues with the filesystem. This might not be a problem with libc6 itself, but a side effect of upgrading in combination with some other package (I suspect the init process, so I guess upstart). The fsck run, and the orphaned inodes it finds are holding me back from installing this on a new server - especially since this already happens on a clean install of 10.04.1! p...@ubuntu:~$ lsb_release -rd Description: Ubuntu 10.04.1 LTS Release: 10.04 ii libc6 2.11.1-0ubuntu7.2 Embedded GNU C Library: Shared libraries ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libc6 2.11.1-0ubuntu7.2 ProcVersionSignature: Ubuntu 2.6.32-24.39-server 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-server x86_64 Architecture: amd64 Date: Sun Nov 7 16:17:07 2010 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.2) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eglibc -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum cl...@fewbar.com wrote: This makes sense, because telinit u just sends SIGTERM to upstart, which has no handler, as it was removed by revision 977, and doesn't seem to have been added back. Since SIG_DFL signals are not delivered to init, I'm not sure how umountroot's call to 'telinit u' can help in this case. Unless I'm missing something in upstart's code (quite likely) I think there may still potentially need to be a change in upstart to support re-executing. Hmm, while that handled was removed Upstream, the code should have been retained in the Ubuntu package as part of the telinit u patch. The idea is that rather than doing a full state transfer, Upstart just re-exec's itself and loses all state. That's why we do it as the last thing before unmounting the root on shutdown, because it then doesn't matter about the state - there shouldn't be any. Maybe that part of the patch has been lost? Scott -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Tue, 2010-12-28 at 14:22 +, Scott James Remnant wrote: On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum cl...@fewbar.com wrote: This makes sense, because telinit u just sends SIGTERM to upstart, which has no handler, as it was removed by revision 977, and doesn't seem to have been added back. Since SIG_DFL signals are not delivered to init, I'm not sure how umountroot's call to 'telinit u' can help in this case. Unless I'm missing something in upstart's code (quite likely) I think there may still potentially need to be a change in upstart to support re-executing. Hmm, while that handled was removed Upstream, the code should have been retained in the Ubuntu package as part of the telinit u patch. The idea is that rather than doing a full state transfer, Upstart just re-exec's itself and loses all state. That's why we do it as the last thing before unmounting the root on shutdown, because it then doesn't matter about the state - there shouldn't be any. Maybe that part of the patch has been lost? Ahh, as I suspected I was missing something in upstart's code. That code is cleverly hidden within the package diff. It registers nih_main_term_signal() which calls nih_main_loop_exit(), which tells init to exit after any currently running operation is over. So, it would seem init exits on SIGTERM. I did see it actually exit and end up panicing the kernel once, but only when I sent multiple kills. init should never exit, so should'nt we instead be execcing ourselves again? Will keep digging in, maybe neither are happening as we expect them to, causing this issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Are you sure? I can't find that code at all - it looks like it's been lost somehow On Tue, Dec 28, 2010 at 6:19 PM, Clint Byrum cl...@fewbar.com wrote: On Tue, 2010-12-28 at 14:22 +, Scott James Remnant wrote: On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum cl...@fewbar.com wrote: This makes sense, because telinit u just sends SIGTERM to upstart, which has no handler, as it was removed by revision 977, and doesn't seem to have been added back. Since SIG_DFL signals are not delivered to init, I'm not sure how umountroot's call to 'telinit u' can help in this case. Unless I'm missing something in upstart's code (quite likely) I think there may still potentially need to be a change in upstart to support re-executing. Hmm, while that handled was removed Upstream, the code should have been retained in the Ubuntu package as part of the telinit u patch. The idea is that rather than doing a full state transfer, Upstart just re-exec's itself and loses all state. That's why we do it as the last thing before unmounting the root on shutdown, because it then doesn't matter about the state - there shouldn't be any. Maybe that part of the patch has been lost? Ahh, as I suspected I was missing something in upstart's code. That code is cleverly hidden within the package diff. It registers nih_main_term_signal() which calls nih_main_loop_exit(), which tells init to exit after any currently running operation is over. So, it would seem init exits on SIGTERM. I did see it actually exit and end up panicing the kernel once, but only when I sent multiple kills. init should never exit, so should'nt we instead be execcing ourselves again? Will keep digging in, maybe neither are happening as we expect them to, causing this issue. -- You received this bug notification because you are a member of Upstart Developers, which is subscribed to upstart . https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted Status in Upstart: Invalid Status in “eglibc” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Confirmed Bug description: On a clean install of Ubuntu 10.04.1, after upgrading the offer libc6 upgrade, on the next reboot the root fs can't be properly unmounted (mount: / is busy). This causes fsck to run on boot and of course some minor issues with the filesystem. This might not be a problem with libc6 itself, but a side effect of upgrading in combination with some other package (I suspect the init process, so I guess upstart). The fsck run, and the orphaned inodes it finds are holding me back from installing this on a new server - especially since this already happens on a clean install of 10.04.1! p...@ubuntu:~$ lsb_release -rd Description: Ubuntu 10.04.1 LTS Release: 10.04 ii libc6 2.11.1-0ubuntu7.2 Embedded GNU C Library: Shared libraries ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libc6 2.11.1-0ubuntu7.2 ProcVersionSignature: Ubuntu 2.6.32-24.39-server 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-server x86_64 Architecture: amd64 Date: Sun Nov 7 16:17:07 2010 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.2) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eglibc -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
On Wed, 2010-12-29 at 00:06 +, Scott James Remnant wrote: Are you sure? I can't find that code at all - it looks like it's been lost somehow quite certain.. its a bit tricky to find it in bzr, but this will give it to you for, say, maverick: $ bzr branch lp:ubuntu/maverick/upstart maverick $ cd maverick $ bzr diff -r tag:upstream-0.6.6..tag:0.6.6-3 apt-get source will wrap it up in the .diff.gz for you as well. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
