Hello List      ,

I recently set up a new machine with Version 2.0.1 of the vservers and 
0.30.210 of the util-vserver. It's a vanilla kernel 2.6.15-3 on a debian host 
on a AMD 64 3200+.

There I discovered some problems with the startup of services inside the 
vservers (debian guests). Zope instances that are started through 
init-scripts fail and die after some time without any further notice. 
Starting them after the init-procedure works as it should. I fear that this 
is mainly zope-related but it can't be only a mistake with zope since it was 
working perfectly on older vserver-versions. If anybody here had run into a 
similar problem and had solved it I'd gladly accept any hints to the 
solution.

Trying to solve this I started the relevant vservers with the fakeinit-flag 
and the plain initstyle. Now the start of the vserver's init scripts is 
normal but stopping the vserver fails with the notice:

>host:/etc/vservers# vserver testserver 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:
>
>----------------------------------------------------------------------
>12105   120 testserver    ?        SNs    0:00 init [2]
>12254   120 testserver    ?        SNs    0:00 /sbin/syslogd
>12261   120 testserver    ?        SNs    0:00 /usr/lib/exim/exim3 -bd -q30m
>12266   120 testserver    ?        SNs    0:00 /usr/sbin/inetd
>12273   120 testserver    ?        SNs    0:00 /usr/sbin/sshd
>12276   120 testserver    ?        SNs    0:00 /usr/sbin/atd
>12279   120 testserver    ?        SNs    0:00 /usr/sbin/cron
>----------------------------------------------------------------------

Sometimes this list is empty.

I'd be glad if anybody had an idea how to debug this: either start the 
services nomally at vserver-startup (preferred) or getting rid of this 
fakeinit-stop problem.

Everything worked normally on older (might be "ancient" for the developers) 
vserver versions, eg.  vs1.9.5 on a vanilla 2.6.8 kernel with util-vserver 
0.30.207.

Here's the output of vserver-info for the problematic host.
>Versions:
>                   Kernel: 2.6.15.3-vs2.0.1.2-nosmp
>                   VS-API: 0x00020001
>             util-vserver: 0.30.210; Feb 28 2006, 11:06:46
>
>Features:
>                       CC: x86_64-linux-gcc, x86_64-linux-gcc (GCC) 3.3.5 
>(Debian 1:3.3.5-13)
>                      CXX: x86_64-linux-g++, x86_64-linux-g++ (GCC) 3.3.5 
>(Debian 1:3.3.5-13)
>                 CPPFLAGS: ''
>                   CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W'
>                 CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W 
>-fmessage-length=0'
>               build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu
>             Use dietlibc: yes
>       Build C++ programs: yes
>       Build C99 programs: yes
>           Available APIs: v13,net
>            ext2fs Source: e2fsprogs
>    syscall(2) invocation: alternative
>      vserver(2) syscall#: 236/glibc
>
>Paths:
>                   prefix: /usr
>        sysconf-Directory: /etc
>            cfg-Directory: /etc/vservers
>         initrd-Directory: $(sysconfdir)/init.d
>       pkgstate-Directory: /var/run/vservers
>          vserver-Rootdir: /vservers


Thanx in advance

Alexander Goeres
-- 
netzwerk- & systemadministrator
-------------------------------------------
agoeres at lieblinx. net
tel.: +49 (0)30 / 61 20 26 87
fax: +49 (0)30 / 69 00 46 03
-------------------------------------------
lieblinx.net
     we do software
-------------------------------------------
reichenberger straße 125
10999 berlin

http://lieblinx.net
-------------------------------------------
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to