up vote 0 down vote favorite
share [g+] share [fb]

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

link|improve this question
60% accept rate
How was the unstoppable state reached? – Aleksandr Levchuk Oct 6 '11 at 12:17
I'm not really sure. It's a server with multiple containers. One has something in the D state. – Squidly Oct 6 '11 at 12:21
The solution ended up having to reboot the host server to force the container off. – Squidly Oct 11 '11 at 16:31
Stop an unstoppable container? Kind of like immovable object versus unstoppable force? – pauska Nov 24 '11 at 21:52
feedback

2 Answers

up vote 0 down vote

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 ;-)

link|improve this answer
Yea I'm aware of the vzctl stop. That does not stop the container. – Squidly Oct 5 '11 at 13:57
feedback
up vote 0 down vote

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.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.