[pve-devel] backup lock

[lyt_yudi]

hi,all

INFO: starting new backup job: vzdump 121 --remove 0 --mode snapshot --compress 
lzo --storage local --node t3
INFO: Starting Backup of VM 121 (qemu)
INFO: status = running
INFO: VM is locked (backup)
ERROR: Backup of VM 121 failed - command 'qm set 121 --lock backup' failed: 
exit code 25
INFO: Backup job finished with errors
TASK ERROR: job errors

this case must be in cli: qm unlock 121 , for unlock 121

maybe this is a bug :(

Can to increase this feature in the API? or unlock it before new backup job? 


lyt_yudi
lyt_y...@icloud.com





smime.p7s
Description: S/MIME cryptographic signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Dietmar Maurer]

On 12/23/2014 02:58 AM, lyt_yudi wrote:

hi,all

INFO: starting new backup job: vzdump 121 --remove 0 --mode snapshot --compress 
lzo --storage local --node t3
INFO: Starting Backup of VM 121 (qemu)
INFO: status = running
INFO: VM is locked (backup)
ERROR: Backup of VM 121 failed - command 'qm set 121 --lock backup' failed: 
exit code 25
INFO: Backup job finished with errors
TASK ERROR: job errors

this case must be in cli: qm unlock 121 , for unlock 121

maybe this is a bug :(

Can to increase this feature in the API? or unlock it before new backup job?


This indicates that something is wrong, maybe a crashed backup job?
You should check if there is an old backup task still running before 
using unlock.



___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[lyt_yudi]

sorry, forgot send to pve-devel :(

> 在 2014年12月23日，下午12:59，Dietmar Maurer  > 写道：
> 
> This indicates that something is wrong, maybe a crashed backup job?

no, it’s cancel the backup job by manual, and then start new backup job.

> You should check if there is an old backup task still running before using 
> unlock.


there is no old backup task.

thanks.

smime.p7s
Description: S/MIME cryptographic signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[lyt_yudi]

> 在 2014年12月23日，下午1:20，lyt_yudi  写道：
> 
>> This indicates that something is wrong, maybe a crashed backup job?

INFO: starting new backup job: vzdump 121 --remove 0 --mode snapshot --compress 
lzo --storage local --node t3
INFO: Starting Backup of VM 121 (qemu)
INFO: status = running
INFO: update VM 121: -lock backup
INFO: exclude disk 'virtio1' (backup=no)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating archive 
'/var/lib/vz/dump/vzdump-qemu-121-2014_12_23-13_22_52.vma.lzo'
INFO: started backup task 'd7330854-dbb6-4461-aba5-f3b604bcfa34'
INFO: status: 0% (88211456/34359738368), sparse 0% (83898368), duration 3, 29/1 
MB/s
ERROR: interrupted by signal
INFO: aborting backup job

this ERROR is caused by manual cancellation.

maybe this process can be integrated to unlock operation.

thanks.

smime.p7s
Description: S/MIME cryptographic signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Wolfgang Link]

Can you pleas post me your version of PVE.

pveversion -v

because I can't reproduce it at my machine, not on the gui and not at cli.

how do you cancel the job manually?

Regrades 

Wolfgang

> On December 23, 2014 at 6:36 AM lyt_yudi  wrote:
> 
> 
> 
> > 在 2014年12月23日，下午1:20，lyt_yudi  写道：
> > 
> >> This indicates that something is wrong, maybe a crashed backup job?
> 
> INFO: starting new backup job: vzdump 121 --remove 0 --mode snapshot
> --compress lzo --storage local --node t3
> INFO: Starting Backup of VM 121 (qemu)
> INFO: status = running
> INFO: update VM 121: -lock backup
> INFO: exclude disk 'virtio1' (backup=no)
> INFO: backup mode: snapshot
> INFO: ionice priority: 7
> INFO: snapshots found (not included into backup)
> INFO: creating archive
> '/var/lib/vz/dump/vzdump-qemu-121-2014_12_23-13_22_52.vma.lzo'
> INFO: started backup task 'd7330854-dbb6-4461-aba5-f3b604bcfa34'
> INFO: status: 0% (88211456/34359738368), sparse 0% (83898368), duration 3,
> 29/1 MB/s
> ERROR: interrupted by signal
> INFO: aborting backup job
> 
> this ERROR is caused by manual cancellation.
> 
> maybe this process can be integrated to unlock operation.
> 
> thanks.___
> pve-devel mailing list
> pve-devel@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Gökalp Çakıcı]

You can cancel the job via web interface while doing backup job. And i 
try the scenario and reproduce the situation. When you use the stop 
button and try to start the vm it says locked. First you unlock it from 
the command line with qm unlock  and then you can start the vm.


On 12/23/14 9:13 AM, Wolfgang Link wrote:

Can you pleas post me your version of PVE.

pveversion -v

because I can't reproduce it at my machine, not on the gui and not at cli.

how do you cancel the job manually?

Regrades

Wolfgang


On December 23, 2014 at 6:36 AM lyt_yudi  wrote:




在 2014年12月23日，下午1:20，lyt_yudi  写道：


This indicates that something is wrong, maybe a crashed backup job?

INFO: starting new backup job: vzdump 121 --remove 0 --mode snapshot
--compress lzo --storage local --node t3
INFO: Starting Backup of VM 121 (qemu)
INFO: status = running
INFO: update VM 121: -lock backup
INFO: exclude disk 'virtio1' (backup=no)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating archive
'/var/lib/vz/dump/vzdump-qemu-121-2014_12_23-13_22_52.vma.lzo'
INFO: started backup task 'd7330854-dbb6-4461-aba5-f3b604bcfa34'
INFO: status: 0% (88211456/34359738368), sparse 0% (83898368), duration 3,
29/1 MB/s
ERROR: interrupted by signal
INFO: aborting backup job

this ERROR is caused by manual cancellation.

maybe this process can be integrated to unlock operation.

thanks.___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


--
Gokalp Cakici
Pusula Iletisim Hizmetleri
T: +90-212-2134142
F: +90-212-2135958
http://www.pusula.net.tr
http://www.uZmanPosta.com

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[lyt_yudi]

> 在 2014年12月23日，下午3:18，Gökalp Çakıcı  写道：
> 
> You can cancel the job via web interface while doing backup job. And i try 
> the scenario and reproduce the situation. When you use the stop button and 
> try to start the vm it says locked. First you unlock it from the command line 
> with qm unlock  and then you can start the vm.

yes, like do this

# pveversion -v
proxmox-ve-2.6.32: 3.3-139 (running kernel: 3.10.0-5-pve)
pve-manager: 3.3-7 (running version: 3.3-7/bc628e80)
pve-kernel-3.10.0-5-pve: 3.10.0-20
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-34-pve: 2.6.32-139
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-15
qemu-server: 3.3-6
pve-firmware: 1.1-3
libpve-common-perl: 3.0-20
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-26
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-5
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

smime.p7s
Description: S/MIME cryptographic signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Dietmar Maurer]

> > You can cancel the job via web interface while doing backup job. And i try
> > the scenario and reproduce the situation. When you use the stop button and
> > try to start the vm it says locked. First you unlock it from the command
> > line with qm unlock  and then you can start the vm.
> 

I can confirm that bug.

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[lyt_yudi]

在 2014年12月23日，下午11:35，Dietmar Maurer  写道：
> 
> 
>>> You can cancel the job via web interface while doing backup job. And i try
>>> the scenario and reproduce the situation. When you use the stop button and
>>> try to start the vm it says locked. First you unlock it from the command
>>> line with qm unlock  and then you can start the vm.
>> 
> 
> I can confirm that bug.
> 

Thanks you.

smime.p7s
Description: S/MIME cryptographic signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Lindsay Mathieson]

On Tue, 23 Dec 2014 04:35:09 PM Dietmar Maurer wrote:
> > > You can cancel the job via web interface while doing backup job. And i
> > > try
> > > the scenario and reproduce the situation. When you use the stop button
> > > and
> > > try to start the vm it says locked. First you unlock it from the command
> > > line with qm unlock  and then you can start the vm.
> >
> > 
> 
> I can confirm that bug.


TBH, I've been seeing this for months, I presumed it was well known.

Happens when a backup fails as well - last power outage we had was in the 
middle of backups and two VM's refused to start on node start because they 
were locked
-- 
Lindsay

signature.asc
Description: This is a digitally signed message part.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Dietmar Maurer]

> > I can confirm that bug.
> 
> 
> TBH, I've been seeing this for months, I presumed it was well known.
> 
> Happens when a backup fails as well - last power outage we had was in the 
> middle of backups and two VM's refused to start on node start because they 
> were locked

Well, this is a different problem.

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Lindsay Mathieson]

On Wed, 24 Dec 2014 09:29:18 AM Dietmar Maurer wrote:
> > Happens when a backup fails as well - last power outage we had was in the 
> > middle of backups and two VM's refused to start on node start because
> > they 
> > were locked
> 
> Well, this is a different problem.


is it? vm is locked because backup failed or was cancelled - looks similar.
-- 
Lindsay

signature.asc
Description: This is a digitally signed message part.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Dietmar Maurer]

> On Wed, 24 Dec 2014 09:29:18 AM Dietmar Maurer wrote:
> > > Happens when a backup fails as well - last power outage we had was in the 
> > > middle of backups and two VM's refused to start on node start because
> > > they 
> > > were locked
> > 
> > Well, this is a different problem.
> 
> 
> is it? vm is locked because backup failed or was cancelled - looks similar.

On power failure, it is impossible to remove the lock, because we are already
dead.
I guess we should remove that lock when we start a node.

But this bug is about removing the lock after receiving a signal (TERM).

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Lindsay Mathieson]

On Wed, 24 Dec 2014 11:57:52 AM Dietmar Maurer wrote:
> On power failure, it is impossible to remove the lock, because we are
> already dead.
> I guess we should remove that lock when we start a node.
> 
> But this bug is about removing the lock after receiving a signal (TERM).

Ah yes, I see your point.

We have a UPS and I thought it signalled a proper shutdown, but  I'm not sure 
- I'll try a test.
-- 
Lindsay

signature.asc
Description: This is a digitally signed message part.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Dietmar Maurer]

> On Wed, 24 Dec 2014 11:57:52 AM Dietmar Maurer wrote:
> > On power failure, it is impossible to remove the lock, because we are
> > already dead.
> > I guess we should remove that lock when we start a node.
> > 
> > But this bug is about removing the lock after receiving a signal (TERM).
> 
> Ah yes, I see your point.
> 
> We have a UPS and I thought it signalled a proper shutdown, but  I'm not sure 
> - I'll try a test.

Ah, and this is one more case ;-) I guess we should terminate all backup
tasks at shutdown (what about other tasks like storage migrate?

AFAIK this is currently not implemented.

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] backup lock

[Lindsay Mathieson]

On Wed, 24 Dec 2014 01:53:40 PM Dietmar Maurer wrote:
> > On Wed, 24 Dec 2014 11:57:52 AM Dietmar Maurer wrote:
> > > On power failure, it is impossible to remove the lock, because we are
> > > already dead.
> > > I guess we should remove that lock when we start a node.
> > >
> > >
> > >
> > > But this bug is about removing the lock after receiving a signal (TERM).
> >
> >
> >
> > Ah yes, I see your point.
> >
> >
> >
> > We have a UPS and I thought it signalled a proper shutdown, but  I'm not
> > sure  - I'll try a test.
>
> Ah, and this is one more case  I guess we should terminate all backup
> tasks at shutdown (what about other tasks like storage migrate?


I suspect all tasks should be cleanly killed if possible

>
> AFAIK this is currently not implemented.

Yup :) Just finished my test:


- Scheduled a backup on a node with a autostart VM,

- rebooted the node when it was backing up the VM

- VM shutdown failed with a lock error. That is quite a problem, as the VM is 
then killed.

- Autostart failed with a lock error.


- Manual start of the VM fails with a locked error.

- After unlock, all is ok.


A clean terminate of the backup and unlock of the currently backing up VM is 
needed.

cheers,

--
Lindsay Mathieson


signature.asc
Description: This is a digitally signed message part.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel