Comment 38 for bug 6841

On Wed, Jul 07, 2004 at 01:47:18PM +0200, Helge Hafting wrote:
> # ifdown lo -v
> Configuring interface lo=lo (inet)
> run-parts /etc/network/if-down.d
> ifconfig lo down
> run-parts /etc/network/if-post-down.d
>
> I get the same output, but then it hangs. I broke it with ctrl+C
> and issued the run-parts command manually. It completed
> immediately, so there's something after that that hangs ifdown.

What do your /etc/network/if-down.d and /etc/network/if-post-down.d
directories contain? Actually, it looks like your system tries to do LDAP
stuff while downing lo, which does not make sense to me, there's stuff like
this in your trace:

[pid 3697] connect(3, {sa_family=AF_INET, sin_port=htons(389),
sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EINPROGRESS (Operation now in progress)
[pid 3697] select(1024, NULL, [3], NULL, {30, 0}) = 1 (out [3], left {30,
0})
[pid 3697] getpeername(3, 0xbfffee18, [128]) = -1 ENOTCONN (Transport
endpointis not connected)
[pid 3697] read(3, 0xbfffee13, 1) = -1 ECONNREFUSED (Connection
refused)
[pid 3697] shutdown(3, 2 /* send and receive */) = -1 ENOTCONN (Transport
endpoint is not connected)

Which might be generating those timeouts or deadlocks you observer. I think
this is a configuration issue on your side (or on another package). Maybe
providing more information on your environment and on the scripts that are
getting run by run-parts would help in locating the problem.

Regards

Javier