[Bug 711635] Re: init: post-start can cause respawn to hang
** Summary changed: - mysql update fails waiting for upstart job to respawn + init: post-start can cause respawn to hang ** Changed in: upstart Status: New = Triaged ** Changed in: upstart Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. https://bugs.launchpad.net/bugs/711635 Title: init: post-start can cause respawn to hang -- 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 687535] Re: upstart loses track of ssh daemon after reload ssh
They definitely should be allowed, ssh is actually a canon example of why. Upstart should supervise the sshd daemon, not the login sub-process associated with a particular connection, and certainly not any processes being run inside the login session. Otherwise stop ssh would kill all user logins; and ssh would not respawn on crash if there was still a used logged in (or running screen!) Scott On Mon, Feb 7, 2011 at 5:51 PM, Steve Langasek steve.langa...@canonical.com wrote: I'm not convinced this is true, Clint. Should upstart jobs be allowed to spawn processes that then get orphaned from the POV of the process supervisor? Maybe upstart shouldn't be tracking the new PID, but maybe it should instead be reaping any children left behind? -- You received this bug notification because you are a member of Upstart Developers, which is subscribed to upstart . https://bugs.launchpad.net/bugs/687535 Title: upstart loses track of ssh daemon after reload ssh Status in Upstart: Invalid Status in “openssh” package in Ubuntu: Fix Released Status in “openssh” source package in Lucid: Fix Released Status in “openssh” source package in Maverick: Fix Released Bug description: When sshd gets a signal 1 for reload, it forks a new process and ditches the old. This causes upstart to believe that ssh has crashed, and loses track of it. A second reload (or any other initctl operation on ssh) will thus say: reload: Unknown instance: There would be 2 ways to fix this: 1. Don't have ssh fork on relod, but keep the same pid 2. Use a different mechanism in upstart to keep track of ssh. Maybe a pid file? Just tracking children of the exited ssh won't work, or it might accidentally track a particular session rather than the master, if somebody just happens to log in close to reload time. openssh-server 1:5.3p1-3ubuntu4 upstart 0.6.5-7 Info for Maverick, Lucid SRU IMPACT: if sshd gets a HUP signal, it forks a new process and upstart thinks the process died and loses track of it, so the user/admin uses the ability to stop/start/reload the daemon through upstart. The problem is fixed in Natty 5.6p1-2ubuntu3. See attached patches for Maverick and Lucid. TEST CASE: - install openssh-server - send a HUP signal to sshd - the daemon is restarted, but upstart thinks that it crashed (/var/log/daemon.log): Dec 28 20:59:57 utest-lls32 init: ssh main process ended, respawning Dec 28 20:59:57 utest-lls32 init: ssh main process (1451) terminated with status 255 Dec 28 20:59:57 utest-lls32 init: ssh main process ended, respawning Dec 28 20:59:57 utest-lls32 init: ssh main process (1455) terminated with status 255 Dec 28 20:59:57 utest-lls32 init: ssh respawning too fast, stopped - after this, upstart won't know about sshd, despite the daemon running just fine: root@utest-lls32:~# reload ssh reload: Unknown instance: With the fix applied, the correct behavior is: - send a HUP signal to sshd ps ax |grep sshd kill -HUP sshd - the daemon reloads (/var/log/auth.log): Dec 28 21:37:01 utest-lls32 sshd[742]: Received SIGHUP; restarting. Dec 28 21:37:01 utest-lls32 sshd[742]: Server listening on 0.0.0.0 port 22. Dec 28 21:37:01 utest-lls32 sshd[742]: Server listening on :: port 22. - reloading with upstart gives the same result, and NOT an error message. REGRESSION POTENTIAL: There is a small race condition in sshd between when it forks, and when it listens for incoming connections. The length of the race is lengthened by a very tiny amount by considering sshd started as soon as it has been executed, rather than when it forks. This will only affect jobs that use 'start on started ssh' and immediately connect to it. This is unlikely to cause problems in any real world scenario, given that most of these programs would also have to fork, exec, and open a socket, which is more work than what sshd will be doing in that time. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/687535 Title: upstart loses track of ssh daemon after reload ssh -- 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 687535] Re: upstart loses track of ssh daemon after reload ssh
That being said, the current process tracker is very much not ideal. I'm working on a new one, and will probably post in this week in the form of a test program to be run and played with. Scott On Mon, Feb 7, 2011 at 8:48 PM, Steve Langasek steve.langa...@canonical.com wrote: On Tue, Feb 08, 2011 at 04:14:59AM -, Scott James Remnant wrote: They definitely should be allowed, ssh is actually a canon example of why. Upstart should supervise the sshd daemon, not the login sub-process associated with a particular connection, and certainly not any processes being run inside the login session. Otherwise stop ssh would kill all user logins; and ssh would not respawn on crash if there was still a used logged in (or running screen!) Good point, comment withdrawn. :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- You received this bug notification because you are a member of Upstart Developers, which is subscribed to upstart . https://bugs.launchpad.net/bugs/687535 Title: upstart loses track of ssh daemon after reload ssh Status in Upstart: Invalid Status in “openssh” package in Ubuntu: Fix Released Status in “openssh” source package in Lucid: Fix Released Status in “openssh” source package in Maverick: Fix Released Bug description: When sshd gets a signal 1 for reload, it forks a new process and ditches the old. This causes upstart to believe that ssh has crashed, and loses track of it. A second reload (or any other initctl operation on ssh) will thus say: reload: Unknown instance: There would be 2 ways to fix this: 1. Don't have ssh fork on relod, but keep the same pid 2. Use a different mechanism in upstart to keep track of ssh. Maybe a pid file? Just tracking children of the exited ssh won't work, or it might accidentally track a particular session rather than the master, if somebody just happens to log in close to reload time. openssh-server 1:5.3p1-3ubuntu4 upstart 0.6.5-7 Info for Maverick, Lucid SRU IMPACT: if sshd gets a HUP signal, it forks a new process and upstart thinks the process died and loses track of it, so the user/admin uses the ability to stop/start/reload the daemon through upstart. The problem is fixed in Natty 5.6p1-2ubuntu3. See attached patches for Maverick and Lucid. TEST CASE: - install openssh-server - send a HUP signal to sshd - the daemon is restarted, but upstart thinks that it crashed (/var/log/daemon.log): Dec 28 20:59:57 utest-lls32 init: ssh main process ended, respawning Dec 28 20:59:57 utest-lls32 init: ssh main process (1451) terminated with status 255 Dec 28 20:59:57 utest-lls32 init: ssh main process ended, respawning Dec 28 20:59:57 utest-lls32 init: ssh main process (1455) terminated with status 255 Dec 28 20:59:57 utest-lls32 init: ssh respawning too fast, stopped - after this, upstart won't know about sshd, despite the daemon running just fine: root@utest-lls32:~# reload ssh reload: Unknown instance: With the fix applied, the correct behavior is: - send a HUP signal to sshd ps ax |grep sshd kill -HUP sshd - the daemon reloads (/var/log/auth.log): Dec 28 21:37:01 utest-lls32 sshd[742]: Received SIGHUP; restarting. Dec 28 21:37:01 utest-lls32 sshd[742]: Server listening on 0.0.0.0 port 22. Dec 28 21:37:01 utest-lls32 sshd[742]: Server listening on :: port 22. - reloading with upstart gives the same result, and NOT an error message. REGRESSION POTENTIAL: There is a small race condition in sshd between when it forks, and when it listens for incoming connections. The length of the race is lengthened by a very tiny amount by considering sshd started as soon as it has been executed, rather than when it forks. This will only affect jobs that use 'start on started ssh' and immediately connect to it. This is unlikely to cause problems in any real world scenario, given that most of these programs would also have to fork, exec, and open a socket, which is more work than what sshd will be doing in that time. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/687535 Title: upstart loses track of ssh daemon after reload ssh -- 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
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 104525] Re: default ntp.conf should use pool.ntp.org servers
Thanks for subscribing the Technical Board to this bug. Please add discussion of the default NTP Servers to the agenda for the next Technical Board meeting that you are able to attend, and we will discuss it with you there. Scott On Sun, Jan 23, 2011 at 2:21 AM, Xavier Robin 104...@bugs.launchpad.net wrote: I had nearly forgotten about ntp-servers-list.c. Here is a patch, but I don't know how to format it best… ** Patch added: patched ntp-servers-list.c https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/104525/+attachment/1803799/+files/ntp-servers-list.c.diff -- You received this bug notification because you are a member of Ubuntu Technical Board, which is a direct subscriber. https://bugs.launchpad.net/bugs/104525 Title: default ntp.conf should use pool.ntp.org servers -- technical-board mailing list technical-bo...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in ubuntu. https://bugs.launchpad.net/bugs/104525 Title: default ntp.conf should use pool.ntp.org servers -- 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
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
On Mon, Dec 27, 2010 at 10:17 PM, Clint Byrum cl...@fewbar.com wrote: So this does in fact seem to be caused completely by init holding libraries open. I patched /etc/init.d/umountfs to save the output of lsof just before unmounting root: Yes, now go read /etc/init.d/umountroot ** Changed in: upstart Status: New = Invalid ** Changed in: upstart (Ubuntu) Status: Triaged = Confirmed -- 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 687535] Re: upstart loses track of ssh daemon after reload ssh
Ah, then ssh already had that race. In which case -D seems like a good choice On Mon, Dec 13, 2010 at 11:05 PM, Clint Byrum cl...@fewbar.com wrote: The code looks something like this: [ option parsing, config check, etc ] sshd.c, line 1744: daemon() [ reinit logs, start random number generator, chdir to /, ignore SIGPIPE ] sshd.c, line 1774: server_listen() -- socket(), bind(), listen(), etc. So, there's already a race between considering it started (at the fork caused by daemon()), and sshd listening, right? Its just that now we're considering it started before the config check and option parsing, so that does give any dependent upstart jobs a bigger head start than they already had. -- You received this bug notification because you are a member of Upstart Developers, which is subscribed to upstart . https://bugs.launchpad.net/bugs/687535 Title: upstart loses track of ssh daemon after reload ssh Status in Upstart: New Status in “openssh” package in Ubuntu: Confirmed Status in “openssh” source package in Lucid: Confirmed Status in “openssh” source package in Maverick: Confirmed Bug description: When sshd gets a signal 1 for reload, it forks a new process and ditches the old. This causes upstart to believe that ssh has crashed, and loses track of it. A second reload (or any other initctl operation on ssh) will thus say: reload: Unknown instance: There would be 2 ways to fix this: 1. Don't have ssh fork on relod, but keep the same pid 2. Use a different mechanism in upstart to keep track of ssh. Maybe a pid file? Just tracking children of the exited ssh won't work, or it might accidentally track a particular session rather than the master, if somebody just happens to log in close to reload time. # lsb_release -rd Description:Ubuntu 10.04.1 LTS Release:10.04 # dpkg -l openssh-server | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-==-= ii openssh-server 1:5.3p1-3ubuntu4 secure shell (SSH) server, for secure access from remote machines # dpkg -l upstart Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii upstart0.6.5-7event-based init daemon -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/687535 Title: upstart loses track of ssh daemon after reload ssh -- 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 687535] Re: upstart loses track of ssh daemon after reload ssh
Not using expect fork of course would mean that ssh would be reported as
running before it was actually listening for connections.
On Mon, Dec 13, 2010 at 10:13 PM, Clint Byrum cl...@fewbar.com wrote:
In looking at the code in OpenSSH, the -D flag only affects this portion
of sshd.c, around line 1740:
/*
* If not in debugging mode, and not started from inetd, disconnect
* from the controlling terminal, and fork. The original process
* exits.
*/
if (!(debug_flag || inetd_flag || no_daemon_flag)) {
#ifdef TIOCNOTTY
int fd;
#endif /* TIOCNOTTY */
if (daemon(0, 0) 0)
fatal(daemon() failed: %.200s, strerror(errno));
/* Disconnect from the controlling tty. */
#ifdef TIOCNOTTY
fd = open(_PATH_TTY, O_RDWR | O_NOCTTY);
if (fd = 0) {
(void) ioctl(fd, TIOCNOTTY, NULL);
close(fd);
}
#endif /* TIOCNOTTY */
}
no_daemon_flag isn't used anywhere else in the code.
Consequently, this code is why the daemon forks on reload, because it
re-execs itself, causing this code to be hit. When run with -D, there's
no call to daemon.
The call to daemon should only chdir to / and close stdin/stdout/stderr,
redirecting them to /dev/null. Given that upstart will already have done
that, this is a non issue. The code then ioctl's on stdin to get rid of
the controlling TTY, which also has no effect when run via upstart since
it is connected to /dev/null. I believe this would change the behavior
if we were using console owner, and sshd would exit on control-C in
console if one was using that, but we're not going to do that, nor would
be a reason to do that for sshd.
I tested this on natty and maverick, killing the daemon in various ways,
making sure that user sessions stay alive, and that reloads keep track
of the daemon. I'm confident that this change is safe and will not cause
any operational issues with openssh-server.
I've submitted a merge proposal adding -D and dropping expect fork,
which would fix this bug.
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Clint Byrum (clint-fewbar)
--
You received this bug notification because you are a member of Upstart
Developers, which is subscribed to upstart .
https://bugs.launchpad.net/bugs/687535
Title:
upstart loses track of ssh daemon after reload ssh
Status in Upstart:
New
Status in “openssh” package in Ubuntu:
Confirmed
Status in “openssh” source package in Lucid:
Confirmed
Status in “openssh” source package in Maverick:
Confirmed
Bug description:
When sshd gets a signal 1 for reload, it forks a new process and ditches
the old. This causes upstart to believe that ssh has crashed, and loses
track of it. A second reload (or any other initctl operation on ssh) will
thus say:
reload: Unknown instance:
There would be 2 ways to fix this:
1. Don't have ssh fork on relod, but keep the same pid
2. Use a different mechanism in upstart to keep track of ssh. Maybe a pid
file? Just tracking children of the exited ssh won't work, or it might
accidentally track a particular session rather than the master, if somebody
just happens to log in close to reload time.
# lsb_release -rd
Description:Ubuntu 10.04.1 LTS
Release:10.04
# dpkg -l openssh-server | cat
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion
Description
+++-===-==-=
ii openssh-server 1:5.3p1-3ubuntu4
secure shell (SSH) server, for secure access
from remote machines
# dpkg -l upstart
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionDescription
+++-==-==-
ii upstart0.6.5-7event-based init daemon
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/687535
Title:
upstart loses track of ssh daemon after reload ssh
--
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
[Bug 626723] Re: init script resets isig flag in an incorrect manner
Robbie just pointed me as this bug, so I'm glad to see it's got a fix. Just wanted to confirm that while some of our issues in Lucid *were* plymouth/X interaction issues, we discovered that many of them were - as debugged above - caused by the isig flag being reapplied to /dev/console. We had to patch a few different things, including Upstart, which all felt they had the right to reset /dev/console. If apache is doing stty sane, that is almost certainly the culprit - anything doing that is going to cause issues because the console is *not* supposed to ever be sane (it's graphical at all points) -- init script resets isig flag in an incorrect manner https://bugs.launchpad.net/bugs/626723 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- 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
[Bug 604185] Re: Unable to start vsftpd with upstart if private key
*** This bug is a duplicate of bug 327823 *** https://bugs.launchpad.net/bugs/327823 ** This bug has been marked a duplicate of bug 565890 init: support output of starting tasks to console * You can subscribe to bug 565890 by following this link: https://bugs.edge.launchpad.net/ubuntu/+source/upstart/+bug/565890/+subscribe ** This bug is no longer a duplicate of bug 565890 init: support output of starting tasks to console ** This bug has been marked a duplicate of bug 327823 init: support job output being passed to start/initctl invocation * You can subscribe to bug 327823 by following this link: https://bugs.edge.launchpad.net/upstart/+bug/327823/+subscribe -- Unable to start vsftpd with upstart if private key https://bugs.launchpad.net/bugs/604185 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. -- 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
[Bug 620441] Re: MySQL upstart stop job does not cleanly shutdown mysql
** Changed in: upstart Status: New = Invalid -- MySQL upstart stop job does not cleanly shutdown mysql https://bugs.launchpad.net/bugs/620441 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- 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
[Bug 620441] Re: MySQL upstart stop job does not cleanly shutdown mysql
You can use a pre-stop script/exec to send the proper command to stop mysql and to wait for it to shut down. -- MySQL upstart stop job does not cleanly shutdown mysql https://bugs.launchpad.net/bugs/620441 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- 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 620441] Re: MySQL upstart stop job does not cleanly shutdown mysql
On Tue, 2010-08-24 at 16:23 +, Clint Byrum wrote: Can we abort the stop from pre-stop somehow? Otherwise I'm afraid users will either be left waiting forever, or still sending SIGKILL. You can call start from the pre-stop script, which will return the job to a running state. That being said, Upstart will happily wait forever for pre-stop before sending SIGKILL - so if the database takes a long time to stop, that's ok Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist? -- MySQL upstart stop job does not cleanly shutdown mysql https://bugs.launchpad.net/bugs/620441 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- 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
[Bug 599342] Re: Temporary failure in name resolution
I'm pretty sure mixing and/or like that will have disastrous consequences (bug #447654) - please don't ** Changed in: libvirt (Ubuntu Maverick) Assignee: Scott James Remnant (scott) = Serge Hallyn (serge-hallyn) -- Temporary failure in name resolution https://bugs.launchpad.net/bugs/599342 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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
[Bug 551097] Re: start stop hang on mysql-server (10.0.4 upgrade from 8.04)
** Project changed: upstart = null ** Also affects: mysql-dfsg-5.1 (Ubuntu) Importance: Undecided Status: New -- start stop hang on mysql-server (10.0.4 upgrade from 8.04) https://bugs.launchpad.net/bugs/551097 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- 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
[Bug 494141] Re: CUPS starts after SAMBA; printers are not available
PryGuy: please don't mess with the bug status, it's as it should be - there is an open task on CUPS ** Changed in: upstart (Ubuntu Lucid) Status: Confirmed = Invalid -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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
[Bug 582376] Re: Samba (nmbd) fails to start at boot
** Project changed: upstart = null ** Changed in: null Status: New = Invalid ** Also affects: samba (Ubuntu) Importance: Undecided Status: New -- Samba (nmbd) fails to start at boot https://bugs.launchpad.net/bugs/582376 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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
[Bug 573853] Re: Cannot control squid Unknown instance
This will be an issue with the squid config ** Package changed: upstart (Ubuntu) = squid (Ubuntu) -- Cannot control squid Unknown instance https://bugs.launchpad.net/bugs/573853 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. -- 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
[Bug 494141] Re: CUPS starts after SAMBA; printers are not available
Not it must not. If you want to depend on a service using Upstart, you MUST convert your init script to an Upstart job. ** Changed in: upstart (Ubuntu) Status: New = Invalid ** Changed in: upstart (Ubuntu Lucid) Status: New = Invalid ** Changed in: cups (Ubuntu) Status: Invalid = Confirmed -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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
[Bug 494141] Re: CUPS starts after SAMBA; printers are not available
re-opening CUPS task, the bug here is that CUPS is still using an init script when it should be converted to an Upstart job -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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
[Bug 19797] Re: services restarted from anacron have nice level of 10
The correct fix for this is to migrate to Upstart, which always starts services with the nice level defined in their conf file, not one inherited from the environment ** Summary changed: - apache is restarted with nice level of 10 + services restarted from anacron have nice level of 10 ** Changed in: anacron (Ubuntu) Status: Confirmed = Triaged -- services restarted from anacron have nice level of 10 https://bugs.launchpad.net/bugs/19797 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- 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
[Bug 253895] Re: upgrading to 8.10
I've no idea why this has been reassigned to hostname - dnshostname can fail, it's a bug in the krb5-config package's postinst for not dealing with that ** Package changed: hostname (Ubuntu) = kerberos-configs (Ubuntu) -- upgrading to 8.10 https://bugs.launchpad.net/bugs/253895 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kerberos-configs in ubuntu. -- 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
[Bug 561475] Re: when sysctl net.ipv6.bindv6only=1, xinetd can not bind to both IPv4 and IPv6 on same port
** Changed in: xinetd (Ubuntu) Status: New = Confirmed -- when sysctl net.ipv6.bindv6only=1, xinetd can not bind to both IPv4 and IPv6 on same port https://bugs.launchpad.net/bugs/561475 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xinetd in ubuntu. -- 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
[Bug 43574] Re: Needs Ubuntu-style init script
Strictly speaking, converting it to an Upstart job would be better ** Changed in: xinetd (Ubuntu) Status: Confirmed = Triaged -- Needs Ubuntu-style init script https://bugs.launchpad.net/bugs/43574 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xinetd in ubuntu. -- 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
[Bug 566736] Re: mysqld does not start reliably...
** Package changed: upstart (Ubuntu) = mysql-dfsg-5.1 (Ubuntu) -- mysqld does not start reliably... https://bugs.launchpad.net/bugs/566736 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- 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
[Bug 520273] Re: cron doesn't send mail
Since cron is clearly invoking sendmail and that invokes postfix, I'm guessing it goes missing inside postfix somewhere ** Package changed: cron (Ubuntu) = postfix (Ubuntu) -- cron doesn't send mail https://bugs.launchpad.net/bugs/520273 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in ubuntu. -- 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
[Bug 456806] Re: mountall vomits a shell onto virtual console when you run vi
Have given up with this SRU. Anyone affected can upgrade to Lucid soon enough. ** Changed in: mountall (Ubuntu Karmic) Status: Triaged = Won't Fix ** Changed in: mountall (Ubuntu Karmic) Assignee: Scott James Remnant (scott) = (unassigned) ** Changed in: mountall (Ubuntu Karmic) Milestone: karmic-updates = None -- mountall vomits a shell onto virtual console when you run vi https://bugs.launchpad.net/bugs/456806 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- 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 456806] Re: mountall vomits a shell onto virtual console when you run vi
On Thu, 2010-03-11 at 21:58 +, mrmookie wrote: This is still happening in MARCH! Any way to fix this permanently yet? The fix was NAK'd by artlogic on 2010-01-02; our Stable Release Updates procedure does not allow us to continue with the backport AFAIK Scott -- Scott James Remnant sc...@ubuntu.com -- mountall vomits a shell onto virtual console when you run vi https://bugs.launchpad.net/bugs/456806 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- 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 456806] Re: mountall vomits a shell onto virtual console when you run vi
On Sun, 2009-12-06 at 09:25 +, Micah Gersten wrote: Scott, someone came in asking about this bug, so I figured I'd attach the patch for the SRU. ** Attachment added: Debdiff for Karmic http://launchpadlibrarian.net/36494855/mountall_1.0.1.debdiff This patch is already in the bzr branch for karmic Scott -- Scott James Remnant sc...@ubuntu.com -- mountall vomits a shell onto virtual console when you run vi https://bugs.launchpad.net/bugs/456806 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- 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
[Bug 456806] Re: mountall vomits a shell onto virtual console when you run vi
** Changed in: mountall (Ubuntu Karmic) Status: Fix Committed = Triaged ** Changed in: mountall (Ubuntu) Status: Fix Committed = Triaged -- mountall vomits a shell onto virtual console when you run vi https://bugs.launchpad.net/bugs/456806 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- 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
[Bug 156085] Re: Could not open /proc/bus/usb/devices
** Changed in: usbview (Ubuntu Jaunty) Assignee: Scott James Remnant (scott) = (unassigned) ** Changed in: usbview (Ubuntu) Assignee: Scott James Remnant (scott) = (unassigned) -- Could not open /proc/bus/usb/devices https://bugs.launchpad.net/bugs/156085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in ubuntu. -- 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
[Bug 456806] Re: mountall vomits a shell onto virtual console when you run vi
Oh , I see the problem: change stop on rcS in /etc/init/mountall.conf to: stop on starting rcS Scott -- Scott James Remnant sc...@ubuntu.com ** Changed in: mountall (Ubuntu Karmic) Status: Confirmed = Fix Committed -- mountall vomits a shell onto virtual console when you run vi https://bugs.launchpad.net/bugs/456806 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- 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
[Bug 456806] Re: mountall vomits a shell onto virtual console when you run vi
The fix introduced other regressions, Johan had a better fix ** Changed in: mountall (Ubuntu Karmic) Status: In Progress = Fix Committed -- mountall vomits a shell onto virtual console when you run vi https://bugs.launchpad.net/bugs/456806 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- 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
[Bug 449326] Re: Network services don't start automatically at boot time
upstart should only receive bugs if you can prove they are with the init daemon, remember that just like in sysvinit, it's other packages that ship the configuration files - please don't use it as a dumping ground though original reporter says this is now fixed ** Package changed: upstart (Ubuntu) = openvpn (Ubuntu) ** Changed in: openvpn (Ubuntu) Status: Incomplete = Fix Released -- Network services don't start automatically at boot time https://bugs.launchpad.net/bugs/449326 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- 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
[Bug 438602] Re: Autoregistration of eucalyptus-cc sometimes fails
The dbus-reconnect fix that I assume the Upstart task refers to has been uploaded ** Changed in: upstart (Ubuntu Karmic) Status: Incomplete = Fix Released -- Autoregistration of eucalyptus-cc sometimes fails https://bugs.launchpad.net/bugs/438602 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- 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
[Bug 430075] Re: eucalyptus-nc fail to upgrade to 1.6~bzr746-0ubuntu1
The actual error: EUCALYPTUS not configured! invoke-rc.d: initscript eucalyptus-nc, action start failed. This comes from the eucalyptus-nc init script ** Package changed: ubuntu = eucalyptus (Ubuntu) -- eucalyptus-nc fail to upgrade to 1.6~bzr746-0ubuntu1 https://bugs.launchpad.net/bugs/430075 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- 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 429443] Re: /usr/bin/kvm-ok should be disassociated from kvm
On Mon, 2009-09-14 at 18:33 +, Dustin Kirkland wrote: Daviey suggested util-linux, which looks reasonable to me. Adding a task for both packages. Assuming cjwatson is at least +0 on util-linux, let's remove it from qemu-kvm and add it to util-linux. Only if you do it upstream, please. Scott -- Scott James Remnant sc...@canonical.com -- /usr/bin/kvm-ok should be disassociated from kvm https://bugs.launchpad.net/bugs/429443 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- 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
[Bug 412972] Re: bad signal mask of ssh sessions
Thanks, this confirms what we expected. The TERM signal is being delivered to the process, it's just that the process's mask is set to block that signal and it's still pending. We're not entirely sure yet what causes this bug; it's certainly not a procps or kernel bug, so I'm reassigning to openssh for the time being since that seems to be the key process. ** Package changed: procps (Ubuntu) = openssh (Ubuntu) ** Changed in: openssh (Ubuntu) Status: Incomplete = Confirmed -- bad signal mask of ssh sessions https://bugs.launchpad.net/bugs/412972 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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
[Bug 399954] Re: Karmic Boot hangs at Configuring network interfaces
Thanks Tim. The bug is in the dhcp3-client script, specifically this bit: # Wait for apparmor to load while [ ! -e $AAPROFILES ]; do # If apparmor is not loaded by the time we leave rcS, we go into S from # another runlevel, or are in a non-S runlevel, just exit runlevel | grep -E -q '( [0-9]|[0-9] S)' exit 0 sleep 1 done For various reasons, this is _NEVER_ going to work! Firstly we call ifup from udev for most standard network devices, and this happens very early in the boot sequence. At this point the /var/run/utmp file doesn't exist, so runlevel will output that error and exit because it can't find the file. Secondly runlevel inherently returns undefined data when running through rcS.d, because you have not yet entered a runlevel. rcS.d is not the single-user runlevel, it is the sysinit phase; until this is completed, you are neither in single-user mode *or* multi-user mode. You're still bootstrapping the system. In fact, during rcS.d runlevel will always exit with an error code; if you happen to catch it before /var/run/utmp is created you'll get that error - if you catch it after there won't be a runlevel record in there yet, so you'll get unknown I'm not entirely sure why you're grepping for we go into S from another runlevel, going into the S runlevel (single-user mode) does not invoke anything in rcS.d -- rc1.d is used to do that. I could not find any mention of apparmor in /etc/rc1.d This also doesn't cope with another possibility, that you *boot* into single-user mode. In this case runlevel will output (after finishing rcS.d and running sulogin) N S ie. you entered single-user mode (the S runlevel) directly, without a previous runlevel. Now what happens if you enter rc2 ? Your runlevel output will be: S 2 ie. you entered runlevel 2 from single-user mode. (Booting directly into multi-user mode, you would get N 2 because you booted directly into it - you don't go via single-user to get there) It also occurs to me that this script is incredibly brittle anyway, because it doesn't account for the fact that apparmor may fail to load any profiles. If that happens, you may end up looping forever in S40networking waiting for apparmor profiles to appear. I think this is what happened to Tim. ** Package changed: upstart (Ubuntu) = dhcp3 (Ubuntu) ** Changed in: dhcp3 (Ubuntu) Status: Incomplete = Triaged -- Karmic Boot hangs at Configuring network interfaces https://bugs.launchpad.net/bugs/399954 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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
[Bug 399954] Re: Karmic Boot hangs at Configuring network interfaces
And from an Upstream POV, there's an even more brittle case. Ubuntu happens to have /var/run on a tmpfs, so /var/run/utmp either doesn't exist, is empty, or contains a runlevel (after rcS.d has finished). But that's fairly unique to Ubuntu; other distros like Debian and Fedora probably don't do this. So during rcS.d, instead of not existing, /var/run/utmp exists and contains data from when the machine was last booted! During shutdown we do put a record in there to wipe the runlevel information, but if the machine wasn't cleanly shut down, runlevel might return N 2 during rcS.d before /var/run/utmp is wiped! So, in summary, don't call runlevel during rcS.d -- Karmic Boot hangs at Configuring network interfaces https://bugs.launchpad.net/bugs/399954 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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
[Blueprint swapfile-in-the-installer] Support Swapfiles at Installation
Blueprint changed by Scott James Remnant: Assignee: Scott James Remnant = Dustin Kirkland Whiteboard changed to: One common item is a multiboot setup. If this were implemented, and it would do a mkswap for official swapfiles when activating them, I could share large, contiguous files (e.g. windows PAGEFILE.SYS) among the systems instead of having several large files, one for each OS. If in the installer, there is a partition going to be mounted, allow the user to select a file. As a post-install, add a swapfile manager where files can be selected, created, or removed. scott - I'm not touching the installer ;) -- Support Swapfiles at Installation https://blueprints.edge.launchpad.net/ubuntu/+spec/swapfile-in-the-installer -- 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
[Bug 318781] Re: D-Bus Policy needs checking
** Bug watch added: Debian Bug tracker #510649 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510649 ** Also affects: dnsmasq (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510649 Importance: Unknown Status: Unknown -- D-Bus Policy needs checking https://bugs.launchpad.net/bugs/318781 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in ubuntu. -- 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
[Blueprint webmirrormanager] Web based repository mirror manager
Blueprint changed by Scott James Remnant: Priority: Undefined = Low -- Web based repository mirror manager https://blueprints.edge.launchpad.net/ubuntu/+spec/webmirrormanager -- 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
[Blueprint webmirrormanager] Web based repository mirror manager
Blueprint changed by Scott James Remnant: Priority: Low = Undefined -- Web based repository mirror manager https://blueprints.edge.launchpad.net/ubuntu/+spec/webmirrormanager -- 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
[Blueprint webmirrormanager] Web based repository mirror manager
Blueprint changed by Scott James Remnant: Definition Status: Approved = Discussion -- Web based repository mirror manager https://blueprints.edge.launchpad.net/ubuntu/+spec/webmirrormanager -- 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
[Bug 292293] Re: udev rules for tun device have wrong permisisons
Then that's a bug in OpenVPN, as you've reassigned it to. We're not shipping with default permissions to allow any user to create network tunnels. -- udev rules for tun device have wrong permisisons https://bugs.launchpad.net/bugs/292293 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- 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
[Bug 45842] Re: nfs shares not mounted at startup
sysvinit is a source package that contains, as well as sysvinit itself, the sysv-rc script runner and initscripts that we still do use. -- nfs shares not mounted at startup https://bugs.launchpad.net/bugs/45842 You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. -- 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
[Bug 65230] Re: startup messages continue on screen after first login prompt appears
Something reloaded SSH? :) This will always pop up over your active console until we completely redo the way we do such messages. -- startup messages continue on screen after first login prompt appears https://bugs.launchpad.net/bugs/65230 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- 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
[Bug 65230] Re: startup messages continue on screen after first login prompt appears
Sounds reasonable -- startup messages continue on screen after first login prompt appears https://bugs.launchpad.net/bugs/65230 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- 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
[Bug 203169] Re: status function for init scripts
Thanks Mathias, udev should not have a status function since it will incline people to believe that running /etc/init.d/udev stop or /etc/init.d/udev start will do something useful when infact they can seriously break a system. -- status function for init scripts https://bugs.launchpad.net/bugs/203169 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- 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
