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 ?



2013/12/19 Federico Simoncelli <fsimonce@redhat.com>
----- Original Message -----
> From: "Pascal Jakobi" <pascal.jakobi@gmail.com>
> To: users@ovirt.org
> Sent: Wednesday, December 18, 2013 9:32:00 PM
> Subject: Re: [Users] AcquireHostId problem
>
> sanlock.log :
>
> 2013-12-18 21:23:32+0100 1900 [867]: s1 lockspace
> b2d69b22-a8b8-466c-bf1f-b6e565228238:250:/rhev/data-center/mnt/lab2.home:_home_vdsm_data/b2d69b22-a8b8-466c-bf1f-b6e565228238/dom_md/ids:0
> 2013-12-18 21:23:52+0100 1920 [4238]: s1 wdmd_connect failed -111
> 2013-12-18 21:23:52+0100 1920 [4238]: s1 create_watchdog failed -1
> 2013-12-18 21:23:53+0100 1921 [867]: s1 add_lockspace fail result -203

Hi Pascal,
 is wdmd up and running?

# ps aux | grep wdmd
root      1650  0.0  0.2 13552 3320 ?        SLs  03:49   0:00 wdmd -G sanlock

--
Federico



--
Pascal Jakobi
116 rue de Stalingrad
93100 Montreuil, France
+33 6 87 47 58 19
Pascal.Jakobi@gmail.com