Re: [ovirt-users] how to clean stuck task

2017-11-14 Thread Gianluca Cecchi
In the mean time, as I had to give an answer for the snapshotted VM, I decided to follow one of the suggestions to run engine-setup and so also to pass my engine from 4.1.6 to 4.1.7. And indeed the 2 stale tasks have been cleaned. The lock symbol has gone away from the apex VM too. Probably the

Re: [ovirt-users] how to clean stuck task

2017-11-13 Thread Gianluca Cecchi
On Mon, Nov 13, 2017 at 8:53 PM, Fred Rolland wrote: > For cleaning these "Tasks" entries (which are actually Jobs in the DB), > you will need to use taskcleaner.sh. > The unlock_entity.sh is for removing locks on entities. > ok. Thanks for clarifying the concept. But from

Re: [ovirt-users] how to clean stuck task

2017-11-13 Thread Fred Rolland
For cleaning these "Tasks" entries (which are actually Jobs in the DB), you will need to use taskcleaner.sh. The unlock_entity.sh is for removing locks on entities. Before running the task cleaner, you need to be sure you actually don't have any tasks running in the SPM. Regarding the snapshot

Re: [ovirt-users] how to clean stuck task

2017-11-13 Thread Gianluca Cecchi
On Mon, Nov 13, 2017 at 7:01 PM, Gianluca Cecchi wrote: > > > > I'd prefer to avoid direct manage of the rdbms... > > As it happened on Friday, after running again the command > > PGPASSWORD=... /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t > all -u engine

Re: [ovirt-users] how to clean stuck task

2017-11-13 Thread Gianluca Cecchi
On Mon, Nov 13, 2017 at 5:28 PM, Wesley Stewart wrote: > Is the VM showing as locked? You could try to manually unlocking it. I > did this in a test environment a while back with some success after a vm > was stuck in a "locked" state. Of course the gui and engine should

Re: [ovirt-users] how to clean stuck task

2017-11-13 Thread Wesley Stewart
Is the VM showing as locked? You could try to manually unlocking it. I did this in a test environment a while back with some success after a vm was stuck in a "locked" state. Of course the gui and engine should handle most of this for you, manually mucking around the internal DB can cause some

Re: [ovirt-users] how to clean stuck task

2017-11-13 Thread Gianluca Cecchi
Hello, it seems the same lock (with the same date) has come again in the list of tasks. Now I have two things in "supposed running" tasks: - the "Restoring VM Snapshot Active VM before the preview of VM snaptest" of 8/11 - the "Creating VM Snapshot 13-11-2017-16-30-Danilo for VM apex" (now

Re: [ovirt-users] how to clean stuck task

2017-11-10 Thread Gianluca Cecchi
On Fri, Nov 10, 2017 at 3:48 PM, wrote: > >> > I've seen this behavior too. IIRC the stale cleaning was not instant, it > took some time to be applied. > > Regards. > > Gianluca >> > Confirmed. Quite soon after the command I saw that the status of the "Current" snapshot line

Re: [ovirt-users] how to clean stuck task

2017-11-10 Thread Wesley Stewart
You could also go database diving. I had an issue where I tried to import a VM from my export domain and it just got hung. I tried running the unlock_entity script but it just kept failing. It sat there for months stuck, and found http://lists.ovirt.org/pipermail/users/2015-April/032346.html

Re: [ovirt-users] how to clean stuck task

2017-11-10 Thread nicolas
El 2017-11-10 14:41, Gianluca Cecchi escribió: On Fri, Nov 10, 2017 at 3:34 PM, wrote: oVirt upgrade to 4.1.7 will probably cleanup this stale task. However, if you want to do it before upgrading, run this command:    PGPASSWORD=...

Re: [ovirt-users] how to clean stuck task

2017-11-10 Thread Gianluca Cecchi
On Fri, Nov 10, 2017 at 3:34 PM, wrote: > oVirt upgrade to 4.1.7 will probably cleanup this stale task. However, if > you want to do it before upgrading, run this command: > >PGPASSWORD=... /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh > -t all -u engine > > Note

Re: [ovirt-users] how to clean stuck task

2017-11-10 Thread nicolas
oVirt upgrade to 4.1.7 will probably cleanup this stale task. However, if you want to do it before upgrading, run this command: PGPASSWORD=... /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all -u engine Note that unlock_entity.sh has many flags and this is just an example