Subject: Re: [vserver] vserver-guest: named does not stop...
From: Herbert Poetzl <herbert@13thfloor.at>
Date: Tue, 16 Nov 2010 21:01:44 +0100

On Tue, Nov 16, 2010 at 08:41:50PM +0100, Jarry wrote:
> Hi,
> I have been running chrooted bind in one of my gentoo
> vserver-guest, without problem. Today I upgraded it from
> 9.4.3 to 9.7.1 and  now "named" does not want to stop.
> Whenever I try (in guest) to stop it, it simply hangs:

> # /etc/init.d/named stop
>  * Stopping chrooted named ...
>  * Umounting chroot dirs
>  * Waiting until all named processes are stopped

what is your guest setup?
i.e. 'v/nattribute --get --x/nid <guest id>'

> And nothing more. I have to abort with ctrl+c, but
> named still keeps running.

> When I try to stop guest, I get this message:

> # vserver vs4-dns stop
>  * Stopping local ...                             [ ok ]
>  * Saving random seed...                          [ ok ]
>  * Stopping chrooted named ...
>  * Umounting chroot dirs
>  * Waiting until all named processes are stopped
> /usr/lib64/util-vserver/vserver.stop: line 96: 30778 Killed 
>      "${ 
>                NICE_CMD[@]}" "${CHBIND_CMD[@]}" "$_VSPACE" --enter 
> "$S_CONTEXT" "${OPTS_VSPACE[ 
>                                   @]}" -- "$_VTAG" --migrate 
> "${OPTS_VTAG_ENTER[@]}" --silent -- $_VCONTEXT $SILEN 
>                                                            T_OPT 
> --migrate --chroot --xid "$S_CONTEXT" -- "${INITCMD_STOP[@]}"
> A timeout occured while waiting for the vserver to finish and it will
> be killed by sending a SIGKILL signal. The following process list
> might be useful for finding out the reason of this behavior:

> ----------------------------------------------------------------------
> 30778  4000 vs4-dns       pts/0    S+     0:00  | 
> \_ /sbin 
>               /rc shutdown
> 30815  4000 vs4-dns       pts/0    S+     0:00  | 
>     \_ / 
>                sbin/runscript /etc/init.d/named --lockfd 6 stop
> 30816  4000 vs4-dns       pts/0    S+     0:00  | 
> 
>                \_ /bin/sh /lib64/rc/sh/runscript.sh /etc/init.d/named stop
> 30954  4000 vs4-dns       pts/0    S+     0:00  | 
> 
>                    \_ sleep 1
> 26957  4000 vs4-dns       ?        S      0:00 supervising syslog-ng
> 26958  4000 vs4-dns       ?        Ss     0:00  \_ /usr/sbin/syslog-ng
> 27030  4000 vs4-dns       ?        Ss     0:00 /usr/sbin/named -u named 
> -t /chroot/dns
> ----------------------------------------------------------------------
> obelix ~ #

IIRC, bind communicates via 127.0.0.1 which is
somewhat hardcoded into the config, so my best
guess would be guest misconfiguration ...

we'll know more when we have the details ...

best,
Herbert

> I tried to install bind in host, and it starts and stops as
> expected. So the problem is definitelly somehow tied up with
> vserver-guest. Any ideas? I know bind config changed somehow
> (attached are both old and new config/init), but I can not
> find any clue...

> Jarry
> 
> -- 
> _______________________________________________________________
> This mailbox accepts e-mails only from selected mailing-lists!
> Everything else is considered to be spam and therefore deleted.