Your message dated Fri, 1 Jun 2012 22:48:55 +1000
with message-id
<CANBdODX+Qio8k1n3o9=pkhzzpgpk1qgzc4gtum_2e_nhd+n...@mail.gmail.com>
and subject line Bug#637995: fixed in autofs 5.0.6-1
has caused the Debian Bug report #637995,
regarding autofs5: shutdown process hangs, because autofs stops too early
sometimes
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
637995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637995
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: autofs5
Version: 5.0.4-3.2
Severity: normal
Occassionally our Debian 6 boxes don't shutdown. The shutdown process
hangs forever with the last messages:
Turning off quotas:...Checking for running unattended-upgrades:
I assume, I found the reason for this issue, but no solution. Our linux
computers mount some directories via NFS. The directories /home and /sw
are managed by the automounter. /usr/local is a symlink to
/sw/local.debian-6 which is mounted from the NFS server. While shutting
down, sometimes the automounter stops too early. Afterwards all
scripts in /etc/init.d which look for binaries in /usr/local/bin hang.
Until Debian 5 this wasn't an issue, because the automounter finishes at
a well defined time relatively to other services. But with the new
dependency based init system, this time seems to vary and sometimes the
automounter finishes too early. If this situation occurs, all local
terminals are already dead and can't be used for debugging. But from an
open ssh session I can restart autofs and then the shutdown goes further.
First I tried to remove /usr/local/bin from the PATH variable in
/etc/profiles. But this doesn't not help, because a lot of init scripts
define theire own PATH variable:
# grep -l "PATH.*/usr/local/bin" /etc/init.d/*
/etc/init.d/alsa-utils
/etc/init.d/apache2
/etc/init.d/binfmt-support
/etc/init.d/cpufrequtils
/etc/init.d/cups
/etc/init.d/hal
/etc/init.d/ipmievd
/etc/init.d/libvirt-bin
/etc/init.d/networking
/etc/init.d/quota
/etc/init.d/quotarpc
/etc/init.d/saned
/etc/init.d/schroot
/etc/init.d/sysstat
/etc/init.d/unattended-upgrades
Next we tried to adjust the start/stop dependencies in /etc/init.d/autofs. But
we didn't found a working solution.
I am not shure, whether autofs is the only reason for the shutdown hang.
Maybe NFS stops too early, too. Maybe it is important to state, that we
don't use the Network-Manger. It caused some problems while system start.
Is there a simple solution or workaround for this?
Ingo
-- System Information:
Debian Release: 6.0.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages autofs5 depends on:
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii ucf 3.0025+nmu1 Update Configuration File: preserv
Versions of packages autofs5 recommends:
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
ii nfs-common 1:1.2.2-4 NFS support files common to client
autofs5 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: autofs
Source-Version: 5.0.6-1
We believe that the bug you reported is fixed in the latest version of
autofs, which is installed in the Debian FTP archive.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
--- End Message ---
