From: Henrik Heil (hhml_at_zweipol.net)
Date: Tue 07 Sep 2004 - 20:38:58 BST
Hello,
after playing with the stable branch for some time i decided to give the
development vserver a try an ran into some problems with fakeinit and a
fixed context id.
i know have linux-2.4.26(kernel.org), patch-2.4.26-vs1.3.9 and
util-vserver-0.29.209, root server distro ist debian woody, vserver
distro is debian sarge.
i need fakeinit because i want to use runit as the vserver-init.
(cmd.start is /sbin/runit)
when i use the fakeinit flag and a fixed context id the vserver start
works fine and the vserver starts with the configured context (1000)
server078:~# vserver-stat
CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME
0 25 29.8M 3K 0m05s37 0m08s81 46m31s21 root server
1000 2 60K 12 0m00s10 0m00s00 0m14s64 sarge-template
when i try to stop the vserver i get the following debug output:
++ /usr/local/sbin/vserver-info - FEATURE vkill
+++ /usr/local/sbin/vserver-info 23 INITPID
++ initpid=-338076288
++ /usr/local/sbin/vkill -s INT -- -338076288
vkill: vc_ctx_kill(): No such process
++ fail=1
This looks to me like the fakeinit INITPID is wrong -338076288 ? and
cannot be killed. However the vserver seems to be down.
server078:~# vserver-stat
CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME
0 25 29.8M 3K 0m05s53 0m08s95 51m27s21 root server
When i try to start the server again (wihout changing the configuration)
i get the following debug output:
++ /usr/local/sbin/vserver-info - FEATURE migrate
++ /usr/local/sbin/chbind --silent --ip 192.168.0.45/24
/usr/local/lib/util-vserver/exec-ulimit /usr/local/etc/vservers/sarge-te
mplate/ulimits /usr/local/lib/util-vserver/chcontext-compat --silent
--secure --ctx 1000 --disconnect --flag fakeinit /usr/local
/lib/util-vserver/save_ctxinfo /usr/local/etc/vservers/sarge-template
/usr/local/lib/util-vserver/clearenv /usr/local/lib/util-v
server/capchroot . /sbin/runit
chcontext: vc_new_s_context(): Operation not permitted
+ cleanup
The server does not start. When i now change the fixed context id (to
1001 or something not used before) the vserver starts again and
everything looks o.k.
It seems that the first "vserver stop" didn't free the context id or
something like that. How can i confirm that the context 1000 ist still
"used" and how can i fix this?
The problem appears regardless of the configured cmd.stop.
Any help is appreciated.
Btw. -- is there more documenation for the new utils and configuration
than
http://www-user.tu-chemnitz.de/~ensc/util-vserver/doc/conf/configuration.html
example-setups or something like that?
Regards,
Henrik
-- Henrik Heil, zweipol Coy & Heil GbR http://www.zweipol.net/ _______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver