OpenVZ Forum


Home » Mailing lists » Users » CT freeze on chkpnt --suspend operation, need advice, nothing can't kill it
CT freeze on chkpnt --suspend operation, need advice, nothing can't kill it [message #45563] Mon, 19 March 2012 17:01 Go to next message
Stoyan Stoyanov is currently offline  Stoyan Stoyanov
Messages: 11
Registered: November 2011
Junior Member
From: *parallels.com
Hi All,

everyday in daily cron, I make vzbackup on running VMs, ok. in the
usual way with suspend,rsync,resume,etc.. BUT from time to time in a
'random' way one of the containers freeze on the vzctl chkpnt VEID --
suspend. With free I mean absolutely :), so the container is unstopble
(with the timeout).
of course it's locked, so need to remove the lock, and then test to
stop, but it timeouts..
ok let me be more brief:
vzctl stop vid -> timeout
vzctl chkpnt vid --kill -> Can not join cpt context 0: (may be becuse
of lock file)
the vm in the container is aboslutely unaccessible, no ip access, no
services(in vm) access.
when try to force kill of the all process on that vm.., they can not
be killed :), I mean no one of them can not be kill -9 processname,

They only way is to restart the node, but it must be reset from the
button, cuz it timeout the vzctl start-stop process :):)

So , is this happen to someone of you, or did you need some particular
detail that I can provide for the purpose of investigation.??



Stoyan Stoyanov
Core System Administrator




CONFIDENTIAL
The information contained in this email and any attachment is
confidential. It is intended only for the named addressee(s). If you
are not the named addressee(s) please notify the sender immediately
and do not disclose, copy or distribute the contents to any other
person other than the intended addressee(s).
Re: CT freeze on chkpnt --suspend operation, need advice, nothing can't kill it [message #45564 is a reply to message #45563] Mon, 19 March 2012 17:22 Go to previous messageGo to next message
Martin Dobrev is currently offline  Martin Dobrev
Messages: 14
Registered: November 2006
Junior Member
From: *parallels.com
Hi,

Do you get any kernel messages in CT0? Any messages in the container? If it's not responsive, you can still access the files from CT0 under /vz/{private,root}/<CTID>/var/log

Martin Dobrev

Sent from iPhonespam SPAMSPAM 4

On 19.03.2012, at 19:01, Stoyan Stoyanov <s.stoianov@maxtelecom.bg> wrote:

> Hi All,
>
> everyday in daily cron, I make vzbackup on running VMs, ok. in the usual way with suspend,rsync,resume,etc.. BUT from time to time in a 'random' way one of the containers freeze on the vzctl chkpnt VEID --suspend. With free I mean absolutely :), so the container is unstopble (with the timeout).
> of course it's locked, so need to remove the lock, and then test to stop, but it timeouts..
> ok let me be more brief:
> vzctl stop vid -> timeout
> vzctl chkpnt vid --kill -> Can not join cpt context 0: (may be becuse of lock file)
> the vm in the container is aboslutely unaccessible, no ip access, no services(in vm) access.
> when try to force kill of the all process on that vm.., they can not be killed :), I mean no one of them can not be kill -9 processname,
>
> They only way is to restart the node, but it must be reset from the button, cuz it timeout the vzctl start-stop process :):)
>
> So , is this happen to someone of you, or did you need some particular detail that I can provide for the purpose of investigation.??
>
>
>
> Stoyan Stoyanov
> Core System Administrator
>
> <maxtelecom-logo.gif>
>
>
> CONFIDENTIAL
> The information contained in this email and any attachment is confidential. It is intended only for the named addressee(s). If you are not the named addressee(s) please notify the sender immediately and do not disclose, copy or distribute the contents to any other person other than the intended addressee(s).
>
Re: CT freeze on chkpnt --suspend operation, need advice, nothing can't kill it [message #45565 is a reply to message #45564] Mon, 19 March 2012 19:06 Go to previous message
Stoyan Stoyanov is currently offline  Stoyan Stoyanov
Messages: 11
Registered: November 2011
Junior Member
From: *parallels.com
Not at all.
kern,daemon,dmesg are rotated and nothing unusual in the past files
messages,syslog,etc, nothing too.


On Mar 19, 2012, at 7:22 PM, Martin Dobrev wrote:

> Hi,
>
> Do you get any kernel messages in CT0? Any messages in the
> container? If it's not responsive, you can still access the files
> from CT0 under /vz/{private,root}/<CTID>/var/log
>
> Martin Dobrev
>
> Sent from iPhonespam SPAMSPAM 4
>
> On 19.03.2012, at 19:01, Stoyan Stoyanov <s.stoianov@maxtelecom.bg>
> wrote:
>
>> Hi All,
>>
>> everyday in daily cron, I make vzbackup on running VMs, ok. in the
>> usual way with suspend,rsync,resume,etc.. BUT from time to time in
>> a 'random' way one of the containers freeze on the vzctl chkpnt
>> VEID --suspend. With free I mean absolutely :), so the container is
>> unstopble (with the timeout).
>> of course it's locked, so need to remove the lock, and then test to
>> stop, but it timeouts..
>> ok let me be more brief:
>> vzctl stop vid -> timeout
>> vzctl chkpnt vid --kill -> Can not join cpt context 0: (may be
>> becuse of lock file)
>> the vm in the container is aboslutely unaccessible, no ip access,
>> no services(in vm) access.
>> when try to force kill of the all process on that vm.., they can
>> not be killed :), I mean no one of them can not be kill -9
>> processname,
>>
>> They only way is to restart the node, but it must be reset from the
>> button, cuz it timeout the vzctl start-stop process :):)
>>
>> So , is this happen to someone of you, or did you need some
>> particular detail that I can provide for the purpose of
>> investigation.??
>>
>>
>>
>> Stoyan Stoyanov
>> Core System Administrator
>>
>> <maxtelecom-logo.gif>
>>
>>
>> CONFIDENTIAL
>> The information contained in this email and any attachment is
>> confidential. It is intended only for the named addressee(s). If
>> you are not the named addressee(s) please notify the sender
>> immediately and do not disclose, copy or distribute the contents to
>> any other person other than the intended addressee(s).
>>
Stoyan Stoyanov
Core System Administrator




CONFIDENTIAL
The information contained in this email and any attachment is
confidential. It is intended only for the named addressee(s). If you
are not the named addressee(s) please notify the sender immediately
and do not disclose, copy or distribute the contents to any other
person other than the intended addressee(s).
Previous Topic: ploop sanity check
Next Topic: iptables LOG
Goto Forum:
  


Current Time: Mon Jun 18 17:08:30 GMT 2018