On Thu, Oct 19, 2006 at 06:37:20PM +0200, Arjan Widlak wrote: > Dear all, > > I entered a vserver directory while in de host > context, /vservers/llink/data/wre and entered the vserver > with vserver llink enter.
that should not affect anything ... > Within the vserver I removed this directory 'wre'. > > I exited this vserver and issued a 'stop' command. > Then I got this error: > > shell-init: could not get current directory: getcwd: > cannot access parent directories: No such file or > directory > cd /vservers not unusual, you removed your current working directory under your shell, no wonder she is complaining :) > After a log time, the vserver would stop, but not completely: > it's still visible, although without name: I'd suspect that is unrelated, but could as well be a side effect of the failing stop > 18:24:10 [514] # vserver-stat > CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME > 0 91 141.9M 53.6M 4d17h35 10h17m09 50d23h57 root server > 49153 23 362.3M 89.4M 55m09s55 8m11s85 50d23h56 cgi > 49154 45 2.5G 1.9G 14h06m28 1h21m11 50d23h56 wg6 > 49155 21 718.6M 456.6M 2d13h16 4h03m51 48d04h26 wg5 > 49182 35 1.2G 812.4M 1h09m44 8m03s10 5d18h20 wg7 > 49187 1 0 0 0m00s00 0m00s00 36m05s11 you should definitely move away from dynamic contexts and have a static context id (2-49151) for each guest > How can I stop this vserver completely. (It's on a production system.) easy, use the vkill command to signal the context and maybe send the proper signal to the 'stuck' process (check with vps auxwww first) I would try the following signals in this order: - CONT - TERM - KILL HTH, Herbert > Any help would be greatly appreciated. > > Kind regards, > -- > Arjan Widlak > United Knowledge | Politiek-digitaal.nl > > _______________________________________________ > Vserver mailing list > [email protected] > http://list.linux-vserver.org/mailman/listinfo/vserver _______________________________________________ Vserver mailing list [email protected] http://list.linux-vserver.org/mailman/listinfo/vserver
