[Users] AcquireHostId problem
fsimonce at redhat.com
Thu Dec 19 23:14:47 UTC 2013
----- Original Message -----
> From: "Pascal Jakobi" <pascal.jakobi at gmail.com>
> To: "Federico Simoncelli" <fsimonce at redhat.com>
> Cc: users at ovirt.org
> Sent: Thursday, December 19, 2013 5:17:59 PM
> Subject: Re: [Users] AcquireHostId problem
> Dec 18 16:46:05 lab2 systemd-wdmd: Starting wdmd: [ OK ]
> Dec 18 16:46:05 lab2 systemd: Unit wdmd.service entered failed state.
> Dec 18 20:52:12 lab2 wdmd: wdmd started S0 H1 G179
> Dec 18 20:52:12 lab2 wdmd: /dev/watchdog0 failed to set timeout
> Dec 18 20:52:12 lab2 wdmd: /dev/watchdog0 disarmed
> Dec 18 20:52:12 lab2 wdmd: /dev/watchdog failed to set timeout
> Dec 18 20:52:12 lab2 wdmd: /dev/watchdog disarmed
> Dec 18 20:52:12 lab2 wdmd: no watchdog device, load a watchdog driver
> Dec 18 20:52:12 lab2 systemd: 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 ?
It seems that you have a watchdog device (probably provided by the
motherboard of your pc/server) that is not currently usable by wdmd.
The temporary workaround to get your system to work is to modprobe
the softdog kernel module and restart wdmd:
# modprobe softdog
# service wdmd restart
Depending on the distribution you're using there are different ways
to automatically load the module at boot, for example on fedora you
and for centos/rhel 6 you can look at the content of:
for an example of how to do the same (e.g. kvm.modules).
That said, in order to get your specific watchdog device to work
properly I'd need some additional information. Can you provide me
the output of these two commands?
# lspci -vvv
More information about the Users