[Bug 1477221] [NEW] Init script fails to stop service
Public bug reported: Init script fails to stop service [Environment] Trusty 14.04.2 [Description] This seems to have been introduced in 1.4.24-2ubuntu0.1 as part of https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1462495. The problem as far as I can see it is that Trustys start-stop-daemon version doesn't handle --pid as expected by the init script. It only knows --pidfile. for pid in $(cat $PIDFILE); do start-stop-daemon --quiet --oknodo --stop \ --retry 5 --pid $pid --exec $HAPROXY || ret=$? done start-stop-daemon treats the argument to --pid as a PID file and therefore tries to open it, which fails. Debugging output: root@ubuntu-1404:~# ps -ef | grep haproxy | grep -v grep haproxy 31802 1 0 16:25 ?00:00:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid root@ubuntu-1404:~# /etc/init.d/haproxy status haproxy is running. root@ubuntu-1404:~# cat /var/run/haproxy.pid 31802 root@ubuntu-1404:~# bash -x /etc/init.d/haproxy stop ... ++ cat /var/run/haproxy.pid + for pid in '$(cat $PIDFILE)' + start-stop-daemon --quiet --oknodo --stop --retry 5 --pid 31802 --exec /usr/sbin/haproxy + '[' 0 -eq 0 ']' + rm -f /var/run/haproxy.pid ... + return 0 + exit 0 root@ubuntu-1404:~# strace -f start-stop-daemon --quiet --oknodo --stop --retry 5 --pid 31802 --exec /usr/sbin/haproxy open(31802, O_RDONLY) = -1 ENOENT (No such file or directory) exit_group(0) = ? +++ exited with 0 +++ root@ubuntu-1404:~# root@ubuntu-1404:~# ps -ef | grep haproxy | grep -v grep haproxy 31802 1 0 16:25 ?00:00:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid root@ubuntu-1404:~# cat /var/run/haproxy.pid cat: /var/run/haproxy.pid: No such file or directory root@ubuntu-1404:~# root@ubuntu-1404:~# dpkg -l haproxy dpkg Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii dpkg 1.17.5ubuntu5.4 amd64 Debian package management system ii haproxy1.4.24-2ubuntu0.1amd64 fast and reliable load balancing reverse proxy root@ubuntu-1404:~# ** Affects: haproxy (Ubuntu) Importance: Undecided Status: New ** Description changed: + Init script fails to stop service + [Environment] Trusty 14.04.2 [Description] This seems to have been introduced in 1.4.24-2ubuntu0.1 as part of https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1462495. The problem as far as I can see it is that Trustys start-stop-daemon version doesn't handle --pid as expected by the init script. It only knows --pidfile. - for pid in $(cat $PIDFILE); do - start-stop-daemon --quiet --oknodo --stop \ - --retry 5 --pid $pid --exec $HAPROXY || ret=$? - done + for pid in $(cat $PIDFILE); do + start-stop-daemon --quiet --oknodo --stop \ + --retry 5 --pid $pid --exec $HAPROXY || ret=$? + done start-stop-daemon treats the argument to --pid as a PID file and therefore tries to open it, which fails. Debugging output: root@ubuntu-1404:~# ps -ef | grep haproxy | grep -v grep haproxy 31802 1 0 16:25 ?00:00:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid root@ubuntu-1404:~# /etc/init.d/haproxy status haproxy is running. - root@ubuntu-1404:~# cat /var/run/haproxy.pid + root@ubuntu-1404:~# cat /var/run/haproxy.pid 31802 root@ubuntu-1404:~# bash -x /etc/init.d/haproxy stop ... ++ cat /var/run/haproxy.pid + for pid in '$(cat $PIDFILE)' + start-stop-daemon --quiet --oknodo --stop --retry 5 --pid 31802 --exec /usr/sbin/haproxy + '[' 0 -eq 0 ']' + rm -f /var/run/haproxy.pid ... + return 0 + exit 0 root@ubuntu-1404:~# strace -f start-stop-daemon --quiet --oknodo --stop --retry 5 --pid 31802 --exec /usr/sbin/haproxy open(31802, O_RDONLY) = -1 ENOENT (No such file or directory) exit_group(0) = ? +++ exited with 0 +++ - root@ubuntu-1404:~# + root@ubuntu-1404:~# root@ubuntu-1404:~# ps -ef | grep haproxy | grep -v grep haproxy 31802 1 0 16:25 ?00:00:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid - root@ubuntu-1404:~# cat /var/run/haproxy.pid + root@ubuntu-1404:~# cat /var/run/haproxy.pid cat: /var/run/haproxy.pid: No such file or directory -
[Bug 1473691] [NEW] Update to latest upstream stable release (3.5)
Public bug reported: Squid's latest stable upstream version is currently 3.5.6 and fixes important bugs, such as the inability to fall back to IPv4 if a websites IPv6 connectivity is broken (e.g. http://readlist.com/lists/squid- cache.org/squid-users/11/58389.html). Please update the package from 3.3.8 to 3.5.6, or, at the very least, update it to version 3.4.8 that Debian already has in its stable distribution (Jessie, and Wheezy backports too). Question 268037 already asked the same - here's the filed bug. ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1473691 Title: Update to latest upstream stable release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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
[Bug 1290819] Re: Update the 7.x trunk for 12.04LTS
** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1290819 Title: Update the 7.x trunk for 12.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1290819/+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
[Bug 1135780] Re: ntp apparmor denied read of /usr/share/samba/upcase.dat
Same issue here (ubuntu 13.10): dmesg: [252470.909606] type=1400 audit(1396308938.493:42): apparmor=DENIED operation=open parent=1 profile=/usr/sbin/ntpd name=/usr/share/samba/upcase.dat pid=26764 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 [252470.909635] type=1400 audit(1396308938.493:43): apparmor=DENIED operation=open parent=1 profile=/usr/sbin/ntpd name=/usr/share/samba/lowcase.dat pid=26764 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 [252470.911005] type=1400 audit(1396308938.493:44): apparmor=DENIED operation=connect parent=1 profile=/usr/sbin/ntpd name=/run/samba/unexpected pid=26764 comm=ntpd requested_mask=rw denied_mask=rw fsuid=0 ouid=0 [252471.393081] type=1400 audit(1396308938.977:45): apparmor=DENIED operation=connect parent=1 profile=/usr/sbin/ntpd name=/run/samba/unexpected pid=26764 comm=ntpd requested_mask=rw denied_mask=rw fsuid=0 ouid=0 [252471.999537] type=1400 audit(1396308939.581:46): apparmor=DENIED operation=connect parent=1 profile=/usr/sbin/ntpd name=/run/samba/unexpected pid=26764 comm=ntpd requested_mask=rw denied_mask=rw fsuid=0 ouid=0 [252472.710900] type=1400 audit(1396308940.293:47): apparmor=DENIED operation=connect parent=1 profile=/usr/sbin/ntpd name=/run/samba/unexpected pid=26764 comm=ntpd requested_mask=rw denied_mask=rw fsuid=0 ouid=0 [252473.343556] type=1400 audit(1396308940.925:48): apparmor=DENIED operation=connect parent=1 profile=/usr/sbin/ntpd name=/run/samba/unexpected pid=26764 comm=ntpd requested_mask=rw denied_mask=rw fsuid=0 ouid=0 As requested nsswitch.conf: # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc Name Service Switch' for information about this file. passwd: compat group: compat shadow: compat hosts: files mdns4_minimal [NOTFOUND=return] wins dns mdns4 #hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 #hosts: files dns wins networks: files protocols: db files services: db files ethers: db files rpc:db files netgroup: nis Installed samba packages: libnss-winbind 3.6.18-1ubuntu3.2K-O i386 Samba nameservice integration plugins libpam-smbpass 3.6.18-1ubuntu3.2K-O i386 pluggable authentication module for Samba libwbclient0 3.6.18-1ubuntu3.2 K-O i386 Samba winbind client library samba 3.6.18-1ubuntu3.2 P-T i386 SMB/CIFS file, print, and login server for Unix samba-common 3.6.18-1ubuntu3.2 P-T all common files used by both the Samba server and client samba-common-bin 3.6.18-1ubuntu3.2 P-T i386 common files used by both the Samba server and client samba-doc 3.6.18-1ubuntu3.2 P-T all Samba documentation winbind 3.6.18-1ubuntu3.2 U-Z i386 Samba nameservice integration server ** Changed in: ntp (Ubuntu) Status: Expired = New -- 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/1135780 Title: ntp apparmor denied read of /usr/share/samba/upcase.dat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1135780/+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
[Bug 1290819] [NEW] Update the 7.x trunk for 12.04LTS
Public bug reported: Will there be an update to the package 7.0.26-1ubuntu1.2 for precise 12.04 with the bug fixed in last weeks USN-2130-1 http://www.ubuntu.com/usn/usn-2130-1/ For now only the 6.x trunk has been updated for precise: Ubuntu 12.04 LTS: libtomcat6-java 6.0.35-1ubuntu3.4 ** Affects: tomcat7 (Ubuntu) Importance: Undecided Status: New ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-4286 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-4322 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-0050 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1290819 Title: Update the 7.x trunk for 12.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1290819/+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
[Bug 1290819] Re: Update the 7.x trunk for 12.04LTS
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-2071 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-2067 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1290819 Title: Update the 7.x trunk for 12.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1290819/+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
[Bug 1091602] Re: Please enhance bind9 to use forwarder addresses from resolvconf
In fact I would like to *continue* to use this feature. It seems have broken with the release upgrade to 13.04. I used to have a file [/var]/run/bind/named.options, created by resolvconf. I think it was done by /etc/resolvconf/update.d/bind. It seems like this file had been removed from resolvconf in 1.53. The changelog fro this version contains: * Remove /etc/resolvconf/update.d/bind (Closes: #608933, #268073). Instead of this, the bind9 package should include a hook script /etc/resolvconf/update.d/bind9 as has been requested in #483098. I really don't care, if this file is moved from resolvconf to bind9 or not, but some package shall provide it. Fortunately I have a backup. I copied the file and the service started to work again. However, I really hate that this will break with every release upgrade. Sp lease get this included with some package again. Here is my use case: I have a local network with some machines, which I want to be able to connect to by name. Hence, I need a name relolution for local names. My solution is to set up a name server on my router, which is authoritative for local names and forwards everything else to my providers name servers. Using resolvconf and bind9, this works fine as long as I configure the provider's name servers in /etc/var/named.conf.options. But what, if the provider changes his nameservers? My service would start to fail and my service is interrupted until I figure out, that the reason is the changed IP addresses of the providers name servers. Resolvconf does have the current IP addresses of the providers name servers. So I want it to generate the forwarders clause for bind9. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1091602 Title: Please enhance bind9 to use forwarder addresses from resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1091602/+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
[Bug 651049] Re: php5: FILTER_VALIDATE_URL will invalidate a hostname that includes '-'
will there be progress here? This is quite an annoying issue as it affects a lot of websites and php frameworks... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/651049 Title: php5: FILTER_VALIDATE_URL will invalidate a hostname that includes '-' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/651049/+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
[Bug 651049] Re: php5: FILTER_VALIDATE_URL will invalidate a hostname that includes '-'
thanks for letting us know! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/651049 Title: php5: FILTER_VALIDATE_URL will invalidate a hostname that includes '-' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/651049/+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
[Bug 531912] Re: /etc/init.d/ssh seems to work, but actually upstart is used.
At least the fix for this bit of Upstart badness is easy enough, just remove /etc/init/ssh and start sshd with the script in init.d. Perhaps it's not as architecturally elegant as Upstart ... Perhaps Ubuntu maintainers are not aware of the importance of sshd in general? sshd is vital on remote machines/servers which are running without screen and keyboard. ssh is the (almost) only access and that has to be reliable! It has to be up as the first daemon as soon as networking is configured and has to be the last service to be stopped on shut down - and it has to restart itself in case of unforseen interruptions. Moving such a service to upstart at the moment is lightheaded and disqualifies Ubuntu for servers. -- 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/531912 Title: /etc/init.d/ssh seems to work, but actually upstart is used. -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Hi Clint, me just came up an idea how we could make this bug hunting more systematic and thoroughly. Up to now we just found some conditions in which shutdown process fails (sshd and portmap). Who tells us that there aren't more daemons which get hardly killed upon shutdown/reboot? So, if for tracing we get a patched '/etc/init.d/umountroot' which does following: on shutdown when the messages init: Re-executing /sbin/init mount: / is busy are issued it indicates that / is not yet umounted. So one could collect the open files (lsof) and write the information to disk. Then wait 5 sec.? untuil the filesystem has commited the journal to disk, try umount again and, if regular umount fails again just do *not* hard restet, but keep system in that state (user can do a cold reboot/shutdown manually). Upon next boot-up the content of the saved processes could be read out and attached to this bug report. This way it should be possible to also detect other daemons not so commonly used, which need their start/stop scrips to be fixed. Re- installing libc6 appears to be a very sensitive trigger to make teses oddities visible. -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
James, did you already upload to proposed (so we'll get binaries tomorrow)? If not, could you be so kind and compile a 'Lucid-amd64 binary' for testing here? -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
I just saw it is a addition to 'umountroot', so I could copy+past form your diff - right? -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
@ Jimmy How do I verify that it works? when system is up and running, issue following command as root and confirm the install when requested: 'apt-get install --reinstall libc6 shutdown -r now' after system has rebooted, check for orphaned inodes with this command (works as user): 'dmesg | grep orphan' and it tells you whether shutdown was clean (no output) or forced (several orphaned inodes). -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
@ James, I verified your patch in Lucid-amd64 (by manually inserting your lines of code) and can confirm: *it works*! (apart from the portmap and rpc.statd issue, whuich still persists of course). I used Clints proposal inserting these 2 lines after the mount commands: /usr/bin/lsof -n | grep DEL sleep 15 (remark: lsof must be given with full path to be found). Now, when portmap is stopped manually before, there is absolutely no more mount: / is busy as without your patch and shutdown is clean! I did many tests with and without your patch - appears to be absolutely reliable. Congratulations! Hope this patch will be inclusded into 10.0.4.2. What now is missing: checking all the daemons which might have a buggy start/stop script. -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Additional remark: I did not observe any noticeble delay of shutdown with the patch. -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Addition (works for me): /usr/bin/lsof -n | grep DEL /lsof.out 21 sleep 15 greps all the open files/libs - if there are any - and writes the information to disk. If there are none one just gets an error message that could not write to ro filesystem. -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
I now de-installed portmap+nfs-common and did install openssh-server: *Only when* I replace the line in /etc/init/ssh.conf by: stop on runlevel [!2345] all is fine with James' patch included! With the original line stop on runlevel S I get a lot of open files, like this: sshd 1385 root DEL REG8,1 185304 /lib/libnss_files-2.11.1.so sshd 1385 root DEL REG8,1 185306 /lib/libnss_nis-2.11.1.so sshd 1385 root DEL REG8,1 185162 /lib/libnss_compat-2.11.1.so.dpkg-new sshd 1385 root DEL REG8,1 185310 /lib/libpthread-2.11.1.so sshd 1385 root DEL REG8,1 185369 /lib/libresolv-2.11.1.so sshd 1385 root DEL REG8,1 185138 /lib/libdl-2.11.1.so sshd 1385 root DEL REG8,1 185156 /lib/libnsl-2.11.1.so sshd 1385 root DEL REG8,1 185083 /lib/libc-2.11.1.so sshd 1385 root DEL REG8,1 185087 /lib/libcrypt-2.11.1.so sshd 1385 root DEL REG8,1 185373 /lib/libutil-2.11.1.so sshd 1385 root DEL REG8,1 184782 /lib/ld-2.11.1.so Insn't that a fast interim fix which can be done by 100 papercuts so it comes in 10.04.2? (sshd is one of the most widely used daemons) would be great! -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
... 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 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
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 -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
BTW: just some minutes ago nwe 'libc6' and 'upstart' was offered as an official update for Lucid. -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
I now stopped portmap by '/etc/init.d/portmap stop' prior to executing 'apt-get install --reinstall libc6 shutdown -r now' and got just the messages init: Re-executing /sbin/init mount: / is busy but no more output from 'lsof' -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
and no more any orphaned inodes (with portmap stopped before)! Congratulations, you are approaching the solution! -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
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? Another observation: sshd cannot be stopped manually: # /etc/init.d/ssh stop * Stopping OpenBSD Secure Shell server sshd [ OK ] but 'daemon.log' tells me it is restarting immediately (and appears with new PID in process list): Feb 1 21:20:20 localhost init: ssh main process (1882) terminated with status 255 Feb 1 21:20:20 localhost init: ssh main process ended, respawning -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
I just checked: portmap is not included in nfs-common, it's a separate package. But it is refereced by nfs-common as required! -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
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) -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
@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 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Clint, seems you are doing an excellent job and I am confident it gets fixed finally! Your proposal works, however only if I modify /etc/init.d/umountroot this way: [ -f /var/run/init.upgraded ] telinit u sleep 1 || : it does *not* work, if I place the sleep in a separate line like this: [ -f /var/run/init.upgraded ] telinit u || : sleep 1 Are you sure that at the end of the line a : (colon) is correct, or should it be a ; (semicolon)? -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
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? -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
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. -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
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?
--
$ dpkg --status libc6
Package: libc6
Status: install ok installed
Priority: required
Section: libs
Installed-Size: 10212
Maintainer: Ubuntu Core developers ubuntu-devel-disc...@lists.ubuntu.com
Architecture: amd64
Source: eglibc
Version: 2.11.1-0ubuntu7.8
Replaces: belocs-locales-bin
Provides: glibc-2.10-1
Depends: libc-bin (= 2.11.1-0ubuntu7.8), debconf (= 0.5) | debconf-2.0,
libgcc1, tzdata, findutils (= 4.4.0-2ubuntu2)
Suggests: glibc-doc, locales
Breaks: nscd ( 2.9)
Conflicts: belocs-locales-bin, tzdata ( 2007k-1), tzdata-etch
---
$ dpkg --status upstart
Package: upstart
Status: install ok installed
Priority: required
Section: admin
Installed-Size: 860
Maintainer: Scott James Remnant sc...@ubuntu.com
Architecture: amd64
Version: 0.6.5-8
Replaces: startup-tasks, system-services, sysvinit, upstart-compat-sysv,
upstart-job
Provides: startup-tasks, system-services, upstart-compat-sysv, upstart-job
Depends: libc6 (= 2.4), libdbus-1-3 (= 1.2.16), libnih-dbus1 (= 1.0.0),
libnih1 (= 1.0.0), libudev0 (= 151-5), sysvinit-utils, sysv-rc, initscripts,
mountall, ifupdown (= 0.6.8ubuntu29)
Breaks: libc6 ( 2.11.1-0ubuntu7.8)
Conflicts: startup-tasks, system-services, sysvinit, upstart-compat-sysv,
upstart-job
Conffiles:
-
$ apt-get install --reinstall libc6 shutdown -r now
-
$ dmesg | grep orphan
[2.898032] EXT3-fs: sda1: orphan cleanup on readonly fs
[2.898051] ext3_orphan_cleanup: deleting unreferenced inode 185613
[2.902163] ext3_orphan_cleanup: deleting unreferenced inode 185601
[2.902430] ext3_orphan_cleanup: deleting unreferenced inode 185574
[2.903374] ext3_orphan_cleanup: deleting unreferenced inode 185553
[2.903771] EXT3-fs: sda1: 4 orphan inodes deleted
--
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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Today again after security update for 'udev' and reboot: 1 orphaned inode. -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Today another libc6 upgrade (security) came in. This is Lucid's file system just after shutdown: # fsck -f /dev/sda6 fsck 1.40.8 (13-Mar-2008) e2fsck 1.40.8 (13-Mar-2008) Lucid: stelle das Journal wieder her Bereinige verwaist Inode 310667 (uid=0, gid=0, mode=0100644, size=51712) Bereinige verwaist Inode 310663 (uid=0, gid=0, mode=0100755, size=1572232) Bereinige verwaist Inode 310661 (uid=0, gid=0, mode=0100755, size=135745) Bereinige verwaist Inode 310651 (uid=0, gid=0, mode=0100644, size=43552) Bereinige verwaist Inode 310650 (uid=0, gid=0, mode=0100644, size=35712) Bereinige verwaist Inode 310644 (uid=0, gid=0, mode=0100644, size=31744) Bereinige verwaist Inode 310640 (uid=0, gid=0, mode=0100755, size=136936) Bereinige verwaist Inode 310639 (uid=0, gid=0, mode=0100644, size=97256) Durchgang 1: Prüfe Inodes, Blocks, und Größen Durchgang 2: Prüfe Verzeichnis Struktur Durchgang 3: Prüfe Verzeichnis Verknüpfungen Durchgang 4: Überprüfe die Referenzzähler Durchgang 5: Überprüfe Gruppe Zusammenfassung Lucid: * DATEISYSTEM WURDE VERÄNDERT * Lucid: 221800/1028160 Dateien (1.2% nicht zusammenhängend), 1258926/4112632 Blöcke -- 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
[Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
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? -- 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
[Bug 688541] Re: race condition on shutdown (leads to corrupted fs)
I do unsubscribe from this bug for the time beeing. It does not make sense to deal with the symtoms until the root of the evil Bug #672177 is fixed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in ubuntu. https://bugs.launchpad.net/bugs/688541 Title: race condition on shutdown (leads to corrupted fs) -- 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 672177] Re: libc6 upgrade causes umount to fail on shutdown
I wonder what Canonical tells its customers who purchased commercial support for Ubuntu in case they discover this bug? Something like: sorry, we have done our best to hide such frightening messages from our customers. Unfortunately the nasty community has retrieved and disclosed it. We have set up plymouth to hide the messages behind a puple splash screen with walking dots and taken provisions, so a normal user won't be able to uninstall plymouth (see Bug #556372). We have switched-off the usual logging from fsck-runs in /var/log/fsck/checkroot and /var/log/fsck/checkfs (see Bug #568594). We have set up the boot process to perform a filesystem check for / at every boot, regaredless what the user specifies in /etc/fstab column #6 (see Bug #568594). Ubuntu firmly relies on 'fsck' as a proven and reliable tool to iron out those minor glitches when your filesystem gets corrupted or marked dirty on shutdown. Moreover we always point out: Ubuntu is not Debian! ??? -- 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 -- 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 688541] Re: race condition on shutdown (leads to corrupted fs)
I first tried to grep within a x-term, but there I get faulty output regarding gvfs. I suppose it's not needed. So I booted into a maintainence root-shell (without network) and did: lsof -n | grep deleted - nothing reported apt-get install --reinstall libc6 and afterwards lsof -n | grep deleted - nothing reported Rebooting brings up the 8 orphaned inodes. May I conclude that reinstall of libc6 package performes correctly and file-system corruption is caused by shutdown process? I am prepared to do more tests, just advise (I am not an expert) and consider local time, I am living east of Greenwich. Merry Christmas, Ingo -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in ubuntu. https://bugs.launchpad.net/bugs/688541 Title: race condition on shutdown (leads to corrupted fs) -- 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 688541] Re: race condition on shutdown (leads to corrupted fs)
And here the output of initctl list after reinstall of libc6. It is amaizeing, that even though I selected root shell without network in the maintainence system, a lot of services including network is up and running (I used scp to copy the output to my PC). ** Attachment added: initctl list output after reinstall of libc6 https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/688541/+attachment/1775392/+files/initctl.out -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in ubuntu. https://bugs.launchpad.net/bugs/688541 Title: race condition on shutdown (leads to corrupted fs) -- 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 688541] Re: race condition on shutdown (leads to corrupted fs)
@Clint: I did test your proposal in Maverick. Before editing the stop scripts: fgrep stop on runlevel /etc/init/*.conf /etc/init/acpid.conf:stop on runlevel [!2345] /etc/init/anacron.conf:stop on runlevel [!2345] /etc/init/apport.conf:stop on runlevel [!2345] /etc/init/atd.conf:stop on runlevel [!2345] /etc/init/cron.conf:stop on runlevel [!2345] /etc/init/cups.conf:stop on runlevel [016] /etc/init/dbus.conf:stop on runlevel [06] /etc/init/failsafe-x.conf:stop on runlevel [06] /etc/init/gdm.conf:stop on runlevel [016] /etc/init/irqbalance.conf:stop on runlevel [!2345] /etc/init/mountall-shell.conf:stop on runlevel [06] /etc/init/rc.conf:stop on runlevel [!$RUNLEVEL] /etc/init/rcS.conf:stop on runlevel [!S] /etc/init/rc-sysinit.conf:stop on runlevel /etc/init/rsyslog.conf:stop on runlevel [06] /etc/init/tty1.conf:stop on runlevel [!2345] /etc/init/tty2.conf:stop on runlevel [!23] /etc/init/tty3.conf:stop on runlevel [!23] /etc/init/tty4.conf:stop on runlevel [!23] /etc/init/tty5.conf:stop on runlevel [!23] /etc/init/tty6.conf:stop on runlevel [!23] /etc/init/udev.conf:stop on runlevel [06] /etc/init/ufw.conf:stop on runlevel [!023456] After editing the stop scripts: fgrep stop on starting /etc/init/*.conf /etc/init/cups.conf:stop on starting rc RUNLEVEL=[016] /etc/init/dbus.conf:stop on starting rc RUNLEVEL=[06] /etc/init/failsafe-x.conf:stop on starting rc RUNLEVEL=[06] /etc/init/gdm.conf:stop on starting rc RUNLEVEL=[016] /etc/init/mountall.conf:stop on starting rcS /etc/init/mountall-shell.conf:stop on starting rc RUNLEVEL=[06] /etc/init/rsyslog.conf:stop on starting rc RUNLEVEL=[06] /etc/init/udev.conf:stop on starting rc RUNLEVEL=[06] Then execute apt-get install --reinstall libc6 and reboot: I still get the 8 orphaned inodes as reported already. Did I miss to change the other scrips as well like this? stop on runlevel [!2345] - stop on stop on starting rc RUNLEVEL=[016] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in ubuntu. https://bugs.launchpad.net/bugs/688541 Title: race condition on shutdown (leads to corrupted fs) -- 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 688541] Re: race condition on shutdown (leads to corrupted fs)
I took you literally and canged all [!2345], not the others: The remaining now are: fgrep stop on runlevel /etc/init/*.conf /etc/init/rc.conf:stop on runlevel [!$RUNLEVEL] /etc/init/rcS.conf:stop on runlevel [!S] /etc/init/rc-sysinit.conf:stop on runlevel /etc/init/tty2.conf:stop on runlevel [!23] /etc/init/tty3.conf:stop on runlevel [!23] /etc/init/tty4.conf:stop on runlevel [!23] /etc/init/tty5.conf:stop on runlevel [!23] /etc/init/tty6.conf:stop on runlevel [!23] /etc/init/ufw.conf:stop on runlevel [!023456] I still get the orphaned inodes. Shall I also convert the tty's? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in ubuntu. https://bugs.launchpad.net/bugs/688541 Title: race condition on shutdown (leads to corrupted fs) -- 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 688541] Re: race condition on shutdown (leads to corrupted fs)
This doesn't affect Debian as the upstart package in Debian still uses plain sysv compat and there are no native upstart jobs yet. A wise decision, good to know. Thanks, Ingo -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in ubuntu. https://bugs.launchpad.net/bugs/688541 Title: race condition on shutdown (leads to corrupted fs) -- 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 688541] Re: race condition on shutdown (leads to corrupted fs)
On Tue, 2010-12-21 at 12:41 +, Scott James Remnant wrote: General note: ubuntu-devel is *NOT* the correct list to discuss Upstart changes unless they're unique to Ubuntu. Wouldn't it be fair to inform Debian about those problems before they release Squeeze? (tough I never observed it on Squeeze till now) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in ubuntu. https://bugs.launchpad.net/bugs/688541 Title: race condition on shutdown (leads to corrupted fs) -- 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 663192] Re: Query with this_.id=? buggy
Filed a mysql bug: http://bugs.mysql.com/bug.php?id=57726 Note that the query is generated by hibernate and is quite common. I guess a lot of packages using hibernate will fail when being run on Ubuntu 10.10. Is there an easy way to install an older/newer version of mysql-server on Ubuntu as a workaround? Tried to install 5.1.51 binaries but the server hangs on startup. ** Bug watch added: MySQL Bug System #57726 http://bugs.mysql.com/bug.php?id=57726 -- Query with this_.id=? buggy https://bugs.launchpad.net/bugs/663192 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-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 663192] [NEW] Query with this_.id=? buggy
Public bug reported: Ubuntu 10.10 mysql-server 5.1.49-1ubuntu8 Query delivers wrong result! In Ubuntu 10.10 the attached query returns no result while in Ubuntu 10.04 with mysql-server 5.1.41 it properly returned the entry with this_.id=1. Note that when omitting the last part of the where clause (and this_.id=1) the query correctly lists all entries. But when adding the additional part to select a specific one nothing is returned. select this_.id as id61_1_, aclkunde3_.akte_acl_kunde_id as akte1_3_, aclkunde_a1_.id as kunde2_3_, aclkunde_a1_.id as id13_0_, aclkunde_a1_.kundennummer as kundennu3_13_0_, aclkunde_a1_1_.anrede as anrede14_0_, aclkunde_a1_1_.vorname as vorname14_0_, aclkunde_a1_1_.zuname as zuname14_0_, aclkunde_a1_2_.anrede as anrede15_0_, aclkunde_a1_2_.vorname as vorname15_0_, aclkunde_a1_2_.zuname as zuname15_0_, case when aclkunde_a1_1_.id is not null then 1 when aclkunde_a1_2_.id is not null then 2 when aclkunde_a1_.id is not null then 0 end as clazz_0_ from akte this_ left outer join akte_kunde aclkunde3_ on this_.id=aclkunde3_.akte_acl_kunde_id left outer join kunde aclkunde_a1_ on aclkunde3_.kunde_id=aclkunde_a1_.id left outer join anwalt aclkunde_a1_1_ on aclkunde_a1_.id=aclkunde_a1_1_.id left outer join kunde_glaeubiger aclkunde_a1_2_ on aclkunde_a1_.id=aclkunde_a1_2_.id where ( aclkunde_a1_.id=1 ) and this_.id=1; ** Affects: mysql-5.1 (Ubuntu) Importance: Undecided Status: New -- Query with this_.id=? buggy https://bugs.launchpad.net/bugs/663192 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-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 663192] Re: Query with this_.id=? buggy
** Attachment added: database sample https://bugs.launchpad.net/bugs/663192/+attachment/1701326/+files/demo_db.sql -- Query with this_.id=? buggy https://bugs.launchpad.net/bugs/663192 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-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 609290] Re: overlapping memcpy in ssl_io_input_read
Can someone please release a fix for this. I have several servers here facing this error. -- overlapping memcpy in ssl_io_input_read https://bugs.launchpad.net/bugs/609290 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 484944] Re: package bacula-director-mysql 2 .4.4-1ubuntu9 failed to install/upgrade: Unterprozes s installiertes post-installation-Skript gab den Fehlerwer t 1 zurück
It Crashed by installing the Package -- package bacula-director-mysql 2.4.4-1ubuntu9 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück https://bugs.launchpad.net/bugs/484944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula 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
