On Sun, Mar 11, 2007 at 02:33:44AM -0500, Chuck wrote:
> there is something in my system that updated recently that has since broken
> vserver's ability to report shutting down guests. I get this kind of report
> on every type of guest. it also appears to be a random thing. other times i
> shut guests down and i get no errors. this variable behavior was only noticed
> yesterday because we are moving physical drives around so we have had to
> stop/start the server otherwise we may not stop any for months. it also waits
> the 'timeout' time before reporting.
>
> as in example below, after this message i try a vps ax|grep 3910 and i find no
> processes with that context running! an immediate restart is error free.
>
> valkyrie boinc # vserver cacti 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:
>
> ----------------------------------------------------------------------
> 14685 3910 cacti ? Ss 0:00 init [3]
> 15181 3910 cacti ? Ss 0:00 \_ /usr/sbin/syslog-ng
> 15245 3910 cacti ? Ssl 0:00 \_ /usr/sbin/named -u named -n
> 4 -t /var/bind
> 15265 3910 cacti ? Ss 0:00 \_ /usr/sbin/apache2 -D
> DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k
> start
> 15266 3910 cacti ? S 0:00 | \_ /usr/sbin/apache2 -D
> DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k
> start
> 15312 3910 cacti ? Sl 0:00 | \_ /usr/sbin/apache2 -D
> DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k
> start
> 15313 3910 cacti ? Sl 0:00 | \_ /usr/sbin/apache2 -D
> DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k
> start
> 15310 3910 cacti ? Ss 0:01 \_ /usr/sbin/clamd
> 15327 3910 cacti ? Ss 0:00 \_ /usr/bin/freshclam -d
> 15468 3910 cacti ? Ss 0:00 \_ /usr/sbin/cron
> 15539 3910 cacti ? Ds 0:00 \_ /sbin/shutdown -r 0 w
> ----------------------------------------------------------------------
> Vserver '/etc/vservers/cacti' still running unexpectedly; please investigate
> it manually...
maybe it takes quite long (timeout +/- something)
and thus, the timeout strikes sometimes ...
I observed similar with qmail, which is quite
strange in shutdown behaviour, especially when
combined with other services ...
(read: it can take between 1 and 10 minutes to
do a proper shutdown)
just and idea,
Herbert
> essentially when it behaves like this, every shutdown says it is still
> running does anyone in gentoo-vserver land have any clue what may be
> causing this apparently false report?
>
> my util-vserver version is 0.30.212-r2
>
> kernel version
>
> 2.6.19-vs2.2.0-rc2
>
>
>
> --
>
> Chuck
>
>
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Sun Mar 11 17:03:03 2007