I'm using vserver-2.0.1 on CentOS. I got the patch in and created a
number of vservers using the "legacy" method, as I wanted the vservers
to be build based upon the base system. Now I am unable to restart or
stop any of the VServers. I can something like this:
[root@asterisk vservers]# vserver vs5 start
WARNING: can not find configuration, assuming legacy
method
Starting the virtual server vs5
Server vs5 is running
[root@asterisk vservers]# vserver vs5 restart
WARNING: can not find configuration, assuming legacy
method
Server vs5 is running
Stopping the virtual server vs5
Server vs5 is running
ipv4root is now 192.168.1.75
New security context is 49156
Stopping HAL daemon: [FAILED]
Stopping sshd: [FAILED]
Stopping portmap: [FAILED]
Shutting down interface eth0:
That's all. No error messages, no more info. The process gets stuck
here. The only I can get the vservers going afresh is by restarting the
base machine. Not the most efficient method I would think. Did I do
something wrong? Any tips? I couldn't find any help on google so far.
Thanks in advance,
Sukrit.D.
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Fri Feb 10 06:25:33 2006