I have an openvz container that is NOT stopping with the standard vz tools. How can I kill it? I tried a VZ destory but that wont work.
Thanks
I have an openvz container that is NOT stopping with the standard vz tools. How can I kill it? I tried a VZ destory but that wont work.
Thanks
Well there is a very tricky part... You have to sort out the init process of the VPS, and kill it, see: http://forum.openvz.org/index.php?t=msg&goto=27976& But... In my opinion you just have one option and that is to restart the HN.
If a VPS get's froozen; look in your syslog if there are any kernel oops, most likely they cause the processes that 'hang'. Furthermore look at the user_beancounters of that particular VPS. Sometime it hangs when installing/upgrading software and if the VPS is not a production one, leave it. It will sort itself in time.
Standard way for solving issue like this is this:
standard vz lists
— What is that? Did you mean "standard vz tools" or what?
Try (and show me with some pastebin service) vzctl exec VE_NUM ps axf
to see what processes are running there and what are theirs states. I had similar problems with OpenVZ on Debian, but I need to be sure that's exactly what I have had.
I assume you know that VE-stopping is made with vzctl stop
;-)
It's a little harsh, but the best way I've found to stop a stubborn container is to forcefully kill the container's processes. Command vzpid
with grep makes it easy to find:
ps ax | awk '{print $1}' | xargs vzpid | grep <container ID> | awk '{print $1}' | xargs kill -9
Now when you run a vzlist -a
it should show the container as "stopped". Better than rebooting the HN imo.
vzctl chkpnt CTID --kill
killing...
Its (most of the time) as simple as that:
vzctl stop [CTID]
if any problems occure go to the lock files (at my install /vz/lock) and rename / delete the lock file named [CTID].lck
vzctl start [CTID]
Voila, you are done.