----- Original Message -----
> From: "Saggi Mizrahi" <smizr...@redhat.com>
> To: "vdsm-devel" <vdsm-de...@fedorahosted.org>
> Cc: "ybronhei" <ybron...@redhat.com>, "Federico Simoncelli"
> <fsimo...@redhat.com>, "Barak Azulay"
> Sent: Sunday, September 23, 2012 1:17:01 PM
> Subject: sanlock issues
> If you are trying to run sanlock on fedora and you get this error:
> Sep 23 11:26:56 dhcp-XX-XX.tlv.redhat.com sanlock: 2012-09-23
> 11:26:56+0200 37014 : wdmd connect failed for watchdog
> You need to do this:
> # unload softdog if it's running
> rmmod softdog
> # Check if there are residual watchdog files under /dev and remove
> rm /dev/watchdog*
> # reload the softdog module
> modprobe softdog
> # make sure the file is named /dev/watchdog
> mv /dev/watchdog? /dev/watchdog
> # set the proper selinux context
> restorecon /dev/watchdog
> # restart wdmd
> systemctl restart wdmd.service
> # restart sanlock
> systemctl restart sanlock.service
> # Profit!
There are several things involved here.
Were multiple watchdog modules loaded? Why? Is the hardware watchdog loaded
after sanlock (which itself loads the softdog)? Is sanlock loading the softdog
even if there in an hardware watchdog present?
It might also be an udev issue with the device naming. You shouldn't need to
relabel the device (another udev issue?).
I doubt that this workaround would survive a reboot (did you check?)
BTW. fedora 17 or 18?
vdsm-devel mailing list