How to remove zombie OpenVZ container?

[tabbi]

Hello,

on my ProxMox VE 1.9 production machine I have one OpenVZ container running a small Debian system I don´t need anymore. But the problem is that it is unstoppable. It runs at 24% CPU usage and 32MB of RAM, but I see no way to halt it. I already tried the web interface commands as well as

# vzctl stop 220
Stopping container ...
Unable to stop container: operation timed out

but nothing stops it.

Is there another way to kill this container? It can be deleted, I don´t use it anymore.

But I hope I don´t have to restart the host node because there are many virtual machines running on it.

Can you help me?

 

[dietmar]

try

# vzctl 220 stop --fast

 

[tabbi]

It is still the same ...

# vzctl stop 220 --fast
Stopping container ...
Unable to stop container: operation timed out

 

[dietmar]

Try to enter the container and kill remaining processes

# vzctl enter 220
cont220# ps auxww
cont220# kill XXX

 

[tabbi]

Enter is also impossible:

# vzctl enter 220
enter into CT 220 failed

 

[dietmar]

Then try vzps to find out what processes are running:

# vzps -E 220

any try to kill them

 

[tabbi]

Thanks for your quick answers! I did the following:

# vzps -E 220
 VEID   PID TTY          TIME CMD
  220  9598 ?        00:00:00 pickup
  220 18795 ?        00:00:06 init
  220 18866 ?        00:00:13 init-logger
  220 19025 ?        00:00:00 portmap
  220 19094 ?        00:00:00 rsyslogd
  220 19103 ?        00:00:00 atd
  220 19123 ?        00:00:00 cron
  220 23245 ?        00:00:00 sshd
  220 23494 ?        106751-23:47:16 master
  220 23501 ?        00:00:00 qmgr
  220 24614 ?        00:00:00 dbus-daemon

And then kill (as root):

kill 24614 23501 23494 23245 19123 19103 19094 19025 18866 18795 9598

But vzps still gives me the same processes. Should I use a special kill option?

 

[dietmar]

Should I use a special kill option?

Well, try '-9' if nothing else helps

 

[tabbi]

This doesn´t change anything, too :-(
Should I restart my host node now or is there another way?

 

[dietmar]

What is the output of

# pveversion -v

But yes, a restart should help anyways.

 

[tabbi]

# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6

 

[dietmar]

Please can you update your system?

 

[tabbi]

via apt-get update && apt-get upgrade?

 

[dietmar]

yes (or aptitude update && aptitude upgrade)

 

[tabbi]

Is this enough?

# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
  proxmox-ve-2.6.32 pve-qemu-kvm
The following packages will be upgraded:
  apache2 apache2-mpm-prefork apache2-utils apache2.2-common pve-firmware
5 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 15.4MB of archives.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]?

Why is proxmox-ve-2.6.32 and pve-qemu-kvm kept back?

 

[dietmar]

Please use

# apt-get dist-upgrade