Søndag 11 september 2005 04:08, skrev Herbert Poetzl:
> > "A timeout occured while waiting for the vserver to finish and it was
> > killed by sending a SIGKILL signal. Please investigate the reasons
> > and/or increase the timeout in apps/vshelper/sync-timeout."
> >
> > on vserver xxx stop. I'm not sure how to debug this.
>
> well, for some reason the guest has still programs
> running after a shutdown, best check with 'vps auxwww'
> and look for processes inside your guest (while waiting
> for the timeout to occur)
OK, you experts have a look at this:
First, minimizing the processes in the vserver to:
templategentoo / # ps ax
PID TTY STAT TIME COMMAND
1 ? S 0:00 init [3]
17335 pts/1 S 0:00 /bin/bash -login
17429 pts/1 R+ 0:00 ps ax
templategentoo / #
Then checking vps on the host:
linuxserver ~ # vps auxwww | grep 100
root 1008 0 MAIN 0.0 0.0 1444 468 ? S<s Sep11
0:00 udevd
root 16616 100 templategentoo 0.0 0.0 1464 496 ? Ss 23:17
0:00 init [3]
root 17335 100 templategentoo 0.0 0.1 2328 1368 pts/1 S+ 23:17
0:00 /bin/bash -login
root 17460 0 MAIN 0.0 0.0 1484 452 pts/8 S+ 23:20
0:00 grep 100
Stopping the vserver from the host:
linuxserver ~ # vserver templategentoo stop
A timeout occured while waiting for the vserver to finish and it was
killed by sending a SIGKILL signal. Please investigate the reasons
and/or increase the timeout in apps/vshelper/sync-timeout.
Before that timeout arrives, checking vps repeatedly from the host:
linuxserver ~ # vps auxwww | grep 100
root 1008 0 MAIN 0.0 0.0 1444 468 ? S<s Sep11
0:00 udevd
root 16616 100 templategentoo 0.0 0.0 1464 496 ? Ss 23:17
0:00 init [3]
root 17335 100 templategentoo 0.0 0.1 2328 1368 pts/1 S+ 23:17
0:00 /bin/bash -login
root 17556 0 MAIN 0.0 0.0 108 28 pts/6 S+ 23:20
0:00 /usr/sbin/vwait --timeout 20 --terminate --status-fd 3 100
root 17612 0 MAIN 0.0 0.0 1484 448 pts/8 S+ 23:20
0:00 grep 100
vwait just waits 20 seconds, and then the vserver is killed.
So I checked to see if it stops the services gracefully first: It doesn't. It
just
goes into that timeout directly without the stopping the init.d scripts:
linuxserver ~ # vps auxwww | grep 100
root 1008 0 MAIN 0.0 0.0 1444 468 ? S<s Sep11
0:00 udevd
root 17832 100 templategentoo 0.0 0.0 1468 500 ? Ss 23:29
0:00 init [3]
root 18403 100 templategentoo 0.0 0.0 1712 664 ? Ss 23:29
0:00 /usr/sbin/syslog-ng
root 18499 100 templategentoo 0.0 0.1 3944 1644 ? Ss 23:29
0:00 /usr/sbin/sshd
root 18522 100 templategentoo 0.0 0.3 7652 3296 ? Ss 23:29
0:00 /usr/sbin/apache2 -k start
apache 18558 100 templategentoo 0.0 0.3 7596 3252 ? S 23:29
0:00 /usr/sbin/apache2 -k start
apache 18559 100 templategentoo 0.0 0.3 7788 3336 ? S 23:29
0:00 /usr/sbin/apache2 -k start
apache 18560 100 templategentoo 0.0 0.3 7788 3336 ? S 23:29
0:00 /usr/sbin/apache2 -k start
apache 18561 100 templategentoo 0.0 0.3 7788 3336 ? S 23:29
0:00 /usr/sbin/apache2 -k start
apache 18562 100 templategentoo 0.0 0.3 7788 3336 ? S 23:29
0:00 /usr/sbin/apache2 -k start
apache 18563 100 templategentoo 0.0 0.3 7788 3336 ? S 23:29
0:00 /usr/sbin/apache2 -k start
root 18608 0 MAIN 0.0 0.0 104 24 pts/6 S+ 23:29
0:00 /usr/sbin/vwait --timeout 20 --terminate --status-fd 3 100
root 18706 0 MAIN 0.0 0.0 1488 452 pts/8 S+ 23:29
0:00 grep 100
Sorry, I have no clue here... This might be a gentoo problem or something
with the init-style (which is 'plain') --- I don't know.
More info:
linuxserver ~ # uname -a
Linux linuxserver 2.6.13-vs2.1.0-pre5-gentoo #1 Sat Sep 10 16:25:41 CEST 2005
i686 AMD Duron(tm) processor AuthenticAMD GNU/Linux
linuxserver ~ # vserver-info
Versions:
Kernel: 2.6.13-vs2.1.0-pre5-gentoo
VS-API: 0x00020001
util-vserver: 0.30.208; Aug 31 2005, 22:13:08
Features:
CC: i386-pc-linux-gnu-gcc, i386-pc-linux-gnu-gcc (GCC)
3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)
CXX: i386-pc-linux-gnu-g++, i386-pc-linux-gnu-g++ (GCC)
3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)
CPPFLAGS: ''
CFLAGS: '-O2 -march=athlon -pipe -fomit-frame-pointer -mmmx
-m3dnow -std=c99 -Wall -pedantic -W'
CXXFLAGS: '-O2 -march=athlon -pipe -fomit-frame-pointer -mmmx
-m3dnow -ansi -Wall -pedantic -W -fmessage-length=0'
build/host: i386-pc-linux-gnu/i386-pc-linux-gnu
Use dietlibc: yes
Build C++ programs: yes
Build C99 programs: yes
Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts
ext2fs Source: e2fsprogs
syscall(2) invocation: alternative
vserver(2) syscall#: 273/glibc
Paths:
prefix: /usr
sysconf-Directory: /etc
cfg-Directory: /etc/vservers
initrd-Directory: /etc/init.d
pkgstate-Directory: /var/run/vservers
Kernelheaders: /lib/modules/2.6.12-vs2.0/build/include
vserver-Rootdir: /vservers
> > /usr/lib/util-vserver/start-vservers -j 1 --all --stop
> > [ ok ]
> > linuxserver ~ # vserver-stat
> > CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME
> > 0 100 1.9G 0.9G 17m11s49 4m12s37 3h24m48 root server
> > 100 3 6.9M 2.7M 0m01s46 0m01s56 1m11s72 templategentoo
> >
> > Vserver still running after start-vserver --all --stop.
>
> did you already file a bugreport on savannah?
Yes, now.
Best regards,
Tor Rune Skoglund
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
