Hello, I have a sanlock problem. I don't fully understand the logs, but from what I can gather, messages like this means it ain't working. 2018-02-16 14:51:46 22123 [15036]: s1 renewal error -107 delta_length 0 last_success 22046 2018-02-16 14:51:47 22124 [15036]: 53977885 aio collect RD 0x7fe5040008c0:0x7fe5040008d0:0x7fe518922000 result -107:0 match res 2018-02-16 14:51:47 22124 [15036]: s1 delta_renew read rv -107 offset 0 /rhev/data-center/mnt/glusterSD/sc5-gluster-10g-1.squaretrade.com:ovirt__images/53977885-0887-48d0-a02c-8d9e3faec93c/dom_md/ids I attempted `hosted-engine --reinitialize-lockspace --force`, which didn't appear to do anything, but who knows. I downed everything and and tried `sanlock direct init -s ....`, which caused sanlock to dump core. At this point the only thing I can think of to do is down everything, whack and manually recreate the lease files and try again. I'm worried that that will lose something that the setup did or will otherwise destroy the installation. It looks like this has been done by others[1], but the references I can find are a bit old, so I'm unsure if that is still a valid approach. So, questions: - Will that work? - Is there something I should do instead of that? Thanks, -j [1] https://bugzilla.redhat.com/show_bug.cgi?id=1116469 _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users