sanlock-2.8-1.fc19.x86_64 Dec 18 16:46:05 lab2 systemd-wdmd[818]: Starting wdmd: [ OK ] Dec 18 16:46:05 lab2 systemd[1]: Unit wdmd.service entered failed state. Dec 18 20:52:12 lab2 wdmd[887]: wdmd started S0 H1 G179 Dec 18 20:52:12 lab2 wdmd[887]: /dev/watchdog0 failed to set timeout Dec 18 20:52:12 lab2 wdmd[887]: /dev/watchdog0 disarmed Dec 18 20:52:12 lab2 wdmd[887]: /dev/watchdog failed to set timeout Dec 18 20:52:12 lab2 wdmd[887]: /dev/watchdog disarmed Dec 18 20:52:12 lab2 wdmd[887]: no watchdog device, load a watchdog driver Dec 18 20:52:12 lab2 systemd[1]: wdmd.service: main process exited, code=exited, status=255/n/a I do not really understand all this. Furthermore, I could not find reference to it in the documentation. Am I missing sthing ? What does "load a wathdog driver" means in concrete ? Thxs again for your help 2013/12/19 Federico Simoncelli <fsimonce@redhat.com>
----- Original Message -----
From: "Pascal Jakobi" <pascal.jakobi@gmail.com> To: "Federico Simoncelli" <fsimonce@redhat.com> Cc: users@ovirt.org Sent: Thursday, December 19, 2013 4:05:07 PM Subject: Re: [Users] AcquireHostId problem
Federico
On may suspect wdmd isn't running as wdmd_connect failed (see sanlock.log). I have ran a "ps" command - no wdmd....
Any idea why wdmd_connect might fail ?
Are you using fedora? What is the version of sanlock? Do you see any information about wdmd in /var/log/messages? Is the wdmd service started?
# service wdmd status # systemctl status wdmd.service
Thanks, -- Federico
-- *Pascal Jakobi* 116 rue de Stalingrad 93100 Montreuil, France *+33 6 87 47 58 19*Pascal.Jakobi@gmail.com