ProxMox web GUI 3.3 with OpenVZ containers get's non usable

[ned]

Here is the screenshot



One of the containers hangs/freezes I can not enter it...and that is the reason proxmox becomes unusable. I know rebooting the server will clear all stuck/zombie processes from the stuck container but this happens on weekly basis and I can not reboot the server every 5 days....

# pveversion
pve-manager/3.3-1/a06c9f73 (running kernel: 2.6.32-32-pve)

Since I do not want to reboot how can I get proxmox web gui to operate? Can I somehow exclude the problem container from the proxmox list? Wne ca container gets stuck I see allot of TIME_WAIT connections to that container. Since I use venet for the containers would the containers be more stable is I used veth?

 

[wolfgang]

Hi,
no you can't do that.
but you can use the cli.
to kill the container and start the pve service new.
if it will not response.

 

[ned]

Hi Wolfgang,

I can not stop the container as it is unstoppable/hung/freezed.

 

[ned]

Can I delete the config file of the containe? Will it then be excluded from proxmox web gui?

 

[wolfgang]

Hi,
you must be able to stop the container with the kill command.

If you delete the config you can't control the container with PVE.

 

[ned]

Hi Wolfgang,

I tried stopping and killing init. See Below.

# vzctl stop 119 --fast
Killing container ...

command does not respond for hours

I find container init with command

for i in `pidof init` ; do  vzpid $i ; echo -n "$i " ; done ;

In my case its pid 30961

I double check with

# vzpid 30961
Pid    CTID    Name
30961    119    init

Status of init process

 ps aux | grep 30961
root       30961  0.0  0.0  30188  2108 ?       [B] Ss[/B]   Mar17   0:00 init

I try to kill init

# kill -9 30961

but it is still there

# ps aux | grep 30961
root       30961  0.0  0.0  30188  2108 ?        Rs   Mar17   0:00 init