[ovirt-users] sanlock issues after 4.3 to 4.4 migration

2022-01-05 Thread Strahil Nikolov via Users
Hello All, I was trying to upgrade my single node setup (Actually it used to be 2+1 arbiter, but one of the data nodes died) from 4.3.10 to 4.4.? The deployment failed on 'hosted-engine --reinitialize-lockspace --force' and it seems that sanlock fails to obtain a lock: # hosted-engine

Re: [ovirt-users] Sanlock issues after upgrading to 3.4

2014-06-11 Thread Maor Lipchuk
Hi Jairo, Can u please open a bug on this at [1]. Also can u please add the logs of the sanlock, vdsm and engine to the bug. [1] https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt Thanks, Maor On 06/07/2014 11:22 PM, Jairo Rizzo wrote: Hello, I have a small 2-node cluster setup

[ovirt-users] Sanlock issues after upgrading to 3.4

2014-06-07 Thread Jairo Rizzo
Hello, I have a small 2-node cluster setup running Glusterfs in replication mode : CentOS v6.5 kernel-2.6.32-431.17.1.el6.x86_64 vdsm-4.14.6-0.el6.x86_64 ovirt-engine-3.4.0-1.el6.noarch (on 1 node) Basically I was running ovirt-engine v 3.3 for months fine and then upgraded to latest version

Re: [Users] sanlock issues (was: help with a presentation)

2012-08-08 Thread Itamar Heim
On 08/08/2012 04:02 AM, Rino Rondan wrote: Hi , I did an install of 3.1 on a desktop using all in one with local data, I had some problem with sanlock socket (/var/run/sanlock), maybe it was for selinux or permission because it have sanlock:sanlock, i change to vdsm:sanlock and permissive

Re: [Users] sanlock issues (was: help with a presentation)

2012-08-08 Thread rino
On Wed, Aug 8, 2012 at 4:31 AM, Itamar Heim ih...@redhat.com wrote: On 08/08/2012 04:02 AM, Rino Rondan wrote: Hi , I did an install of 3.1 on a desktop using all in one with local data, I had some problem with sanlock socket (/var/run/sanlock), maybe it was for selinux or permission

Re: [Users] sanlock issues

2012-08-08 Thread Itamar Heim
On 08/08/2012 12:10 PM, rino wrote: On Wed, Aug 8, 2012 at 4:31 AM, Itamar Heim ih...@redhat.com mailto:ih...@redhat.com wrote: On 08/08/2012 04:02 AM, Rino Rondan wrote: Hi , I did an install of 3.1 on a desktop using all in one with local data, I had some

Re: [Users] sanlock issues

2012-08-07 Thread Mark Wu
On 08/07/2012 02:35 AM, Jacob Wyatt wrote: oVirt Node Hypervisor release 2.5.0 (2.0.fc17) Can't start a VM. Same error in any of /var/log/libvirt/qemu/vmname.log libvir: Locking error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified I've

Re: [Users] sanlock issues

2012-08-07 Thread Mark Wu
@ovirt.orgusers@ovirt.org Ärende: Re: [Users] sanlock issues On 08/07/2012 02:35 AM, Jacob Wyatt wrote: oVirt Node Hypervisor release 2.5.0 (2.0.fc17) Can't start a VM. Same error in any of /var/log/libvirt/qemu/vmname.log libvir: Locking error : unsupported configuration: Read/write, exclusive access

Re: [Users] sanlock issues

2012-08-07 Thread Jacob Wyatt
# grep -v ^# /etc/libvirt/qemu-sanlock.conf auto_disk_leases=0 require_lease_for_disks=0 I did try systemd-vdsmd reconfigure. From: Mark Wu [wu...@linux.vnet.ibm.com] What does grep -v ^# /etc/libvirt/qemu-sanlock.conf say? Have you tried

[Users] sanlock issues

2012-08-07 Thread Jacob Wyatt
Solved with a hack. oVirt Node Hypervisor release 2.5.0 (2.0.fc17) Couldn't start a VM because sanlock wasn't running. Sanlock wasn't running because wdmd wasn't running. wdmd was running because softdog kernel module wasn't loaded. As I didn't know of another way of making the change

Re: [Users] sanlock issues

2012-08-07 Thread Dennis Jacobfeuerborn
On 08/07/2012 04:08 PM, Jacob Wyatt wrote: Solved with a hack. oVirt Node Hypervisor release 2.5.0 (2.0.fc17) Couldn't start a VM because sanlock wasn't running. Sanlock wasn't running because wdmd wasn't running. wdmd was running because softdog kernel module wasn't loaded. As I