Public bug reported: Under Ubuntu 10.04 Lucid, sshd is an upstart job controlled by /etc/init/ssh.conf This file provides for start and stop as follows:
start on filesystem stop on runlevel S At shutdown or reboot, therefore, sshd is not stopped. Since sshd is in /usr/sbin/sshd and also accesses lib files in /usr/lib this means that /etc/rc0.d/S40umountfs cannot successfully umount /usr at shutdown when /usr is on its own partition. This definitely leads to umount reporting errors in the shutdown console messages. It may also lead to fsck running on reboot and problems with mountall... I can't say for certain yet as I am also having problems umounting /var, possibly due to a power failure, which is what led me to notice and investigate these messages. My guess is that when sshd was a System V init process, it was killed by the killall5 process in /etc/rc0.d/S20sendsigs. Under Lucid sshd has been made an upstart job and as such is exempt from the killall5 and so needs to be stopped explicitly. I admit I am by no means an expert on upstart or sshd, but the fix appears to me to be to modify /etc/init/ssh.conf to read stop on runlevel [!2345] ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openssh-server 1:5.3p1-3ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Thu Jul 8 14:45:50 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- sshd never stops, prevents umount of /usr partition https://bugs.launchpad.net/bugs/603363 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