Strange OVZ Issue

Brandon

Hi Everyone,

I am trying to resolve this strange OVZ issue where when rebooting the container, it is automatically killed as soon as it is initiated.

Here is the reboot output:

Restarting container
Starting container...
Opening delta /vz/private/9999/root.hdd/root.hdd
Adding delta dev=/dev/ploop18642 img=/vz/private/9999/root.hdd/root.hdd (rw)
Mounting /dev/ploop18642p1 at /vz/root/9999 fstype=ext4 data='balloon_ino=12,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,'
Container is mounted
Adding IP address(es): xxx.xx.xx.xxx
Setting CPU limit: 300
Setting CPU units: 10000
Setting CPUs: 4
Killing container ...
Container was stopped
Unmounting file system at /vz/root/9999
Unmounting device /dev/ploop18642
Container is unmounted

Does anyone know how to resolve this issue?

timnboys

yes do you have root access to the node(just checking) and do you have any programs like nodewatch that could be stopping it?

Brandon

@timnboys said:
yes do you have root access to the node(just checking) and do you have any programs like nodewatch that could be stopping it?

Yes I have root access. I used to have nodewatch but uninstalled it.

Brandon

This is also the output of dmsg | tail

[4502322.985127] EXT4-fs (ploop52235p1): mounted filesystem with ordered data mode. Opts:
[4502322.985805] EXT4-fs (ploop52235p1): loaded balloon from 12 (46141448 blocks)
[4502322.988694] CT: 9999: started
[4502324.300845] CT: 9999: stopped
[4502341.877178] ploop52235: p1
[4502341.960636] ploop52235: p1
[4502342.049166] EXT4-fs (ploop52235p1): mounted filesystem with ordered data mode. Opts:
[4502342.049604] EXT4-fs (ploop52235p1): loaded balloon from 12 (46141448 blocks)
[4502342.052185] CT: 9999: started
[4502343.290814] CT: 9999: stopped

timnboys

okay was this a container nodewatch suspended before? or you got any alerts from nodewatch about this container?
please try this from nodewatch's manual:

vzctl set VEID --disabled no --save

and see if that helps
as I am guessing nodewatch probably suspended that container and caused this.

Brandon

@timnboys said:
okay was this a container nodewatch suspended before? or you got any alerts from nodewatch about this container?
please try this from nodewatch's manual:
as I am guessing nodewatch probably suspended that container and caused this.

No this container was not disabled before and Nodewatch wasn't active when this happened.

I tried your command and its still continuing with the same behaviour.

timnboys

okay then could you give me your logs please(you know like openvz's actual log for this specific container or openvz's debug log pertain to this container?)

Brandon

@timnboys said:
okay then could you give me your logs please(you know like openvz's actual log for this specific container or openvz's debug log pertain to this container?)

Sent you a PM!