Re: [Users] AcquireHostId problem
- Original Message -
> From: "Pascal Jakobi"
> To: users@ovirt.org
> Sent: Monday, December 23, 2013 5:34:55 PM
> Subject: Re: [Users] AcquireHostId problem
>
> Here is the message I get on the console : Error while executing action
> Attach Storage Domain: AcquireHostIdFailure
> The software seems to go pretty far : it reaches the locked stated before
> failing.
>
> In engine.log
> 2013-12-23 16:56:49,497 ERROR
> [org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand]
> (ajp--127.0.0.1-8702-2) Command
> org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand throw
> Vdc Bll exception. With error message VdcBLLException:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
> VDSGenericException: VDSErrorException: Failed to CreateStoragePoolVDS,
> error = Cannot acquire host id: ('8c626a3f-5846-434e-83d8-6238e1ff9e03',
> SanlockException(-203, 'Sanlock lockspace add failure', 'Sanlock
> exception')) (Failed with error AcquireHostIdFailure and code 661)
>
> Can this help ?
What's the logs in VDSM? Is this the same host where wdmd was up and
running or another one? If you restarted your laptop and you didn't
persist the module loading (following the instruction in one of my
previous emails) you'll end up in the same problem every time.
--
Federico
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
Here is the message I get on the console : Error while executing action
Attach Storage Domain: AcquireHostIdFailure
The software seems to go pretty far : it reaches the locked stated before
failing.
In engine.log
2013-12-23 16:56:49,497 ERROR
[org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand]
(ajp--127.0.0.1-8702-2) Command
org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand throw
Vdc Bll exception. With error message VdcBLLException:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
VDSGenericException: VDSErrorException: Failed to CreateStoragePoolVDS,
error = Cannot acquire host id: ('8c626a3f-5846-434e-83d8-6238e1ff9e03',
SanlockException(-203, 'Sanlock lockspace add failure', 'Sanlock
exception')) (Failed with error AcquireHostIdFailure and code 661)
Can this help ?
2013/12/23 Federico Simoncelli
> - Original Message -
> > From: "Pascal Jakobi"
> > To: users@ovirt.org
> > Sent: Monday, December 23, 2013 4:33:23 PM
> > Subject: Re: [Users] AcquireHostId problem
> >
> > Ok.
> > What I am doing is just adding a new NFS domain that fails : "Failed to
> add
> > Storage Domain DataLab2. (User: admin@internal)"
> > And I thought that the "/dev/watchdog0 failed to set timeout" msg was
> > signalling an error.
>
> No that's just the attempt to use the laptop watchdog but then it
> fallbacks to the softdog one:
>
> Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog1 armed with fire_timeout 60
> Dec 20 23:44:11 lab2 systemd[1]: Started Watchdog Multiplexing Daemon.
>
> --
> Federico
>
--
*Pascal Jakobi*
116 rue de Stalingrad
93100 Montreuil, France
*+33 6 87 47 58 19*pascal.jak...@gmail.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
- Original Message - > From: "Pascal Jakobi" > To: users@ovirt.org > Sent: Monday, December 23, 2013 4:33:23 PM > Subject: Re: [Users] AcquireHostId problem > > Ok. > What I am doing is just adding a new NFS domain that fails : "Failed to add > Storage Domain DataLab2. (User: admin@internal)" > And I thought that the "/dev/watchdog0 failed to set timeout" msg was > signalling an error. No that's just the attempt to use the laptop watchdog but then it fallbacks to the softdog one: Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog1 armed with fire_timeout 60 Dec 20 23:44:11 lab2 systemd[1]: Started Watchdog Multiplexing Daemon. -- Federico ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
Ok. What I am doing is just adding a new NFS domain that fails : "Failed to add Storage Domain DataLab2. (User: admin@internal)" And I thought that the "/dev/watchdog0 failed to set timeout" msg was signalling an error. Will rerun test in 5 minutes. Thxs ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
- Original Message - > From: "Pascal Jakobi" > To: "Federico Simoncelli" > Cc: users@ovirt.org > Sent: Saturday, December 21, 2013 12:37:51 PM > Subject: Re: [Users] AcquireHostId problem > > Nope. Nothing more in logs. > My guess is that the timeout problem generates the error. > However, in reality if you run "mount", you have the target partitions > mounted If you still have a problem and something is not working there's an error somewhere and we only have to find it. Look in the engine logs and in the vdsm logs for any error (not only "Traceback" but also "ERROR"). Try to describe with more details what you're trying to do, what you expect to happen and what is happening instead. > Therefore, I guess the problem is to understand why "dev/watchdog0 failed > to set timeout" The watchdog provided by your laptop is not working properly or it's not able to set the timeout we need. You inserted the softdog module and wdmd is now up and running as you reported with: > 2013/12/21 Federico Simoncelli > > > - Original Message - > > > From: "Pascal Jakobi" > > > To: "Federico Simoncelli" , users@ovirt.org > > > Sent: Friday, December 20, 2013 11:54:21 PM > > > Subject: Re: [Users] AcquireHostId problem > > > > > > Dec 20 23:43:59 lab2 kernel: [183033.639261] softdog: Software Watchdog > > > Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 > > > (nowayout=0) > > > Dec 20 23:44:11 lab2 systemd[1]: Starting Watchdog Multiplexing Daemon... > > > Dec 20 23:44:11 lab2 wdmd[25072]: wdmd started S0 H1 G179 > > > Dec 20 23:44:11 lab2 systemd-wdmd[25066]: Starting wdmd: [ OK ] > > > Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 failed to set timeout > > > Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 disarmed > > > Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog1 armed with fire_timeout > > > 60 > > > Dec 20 23:44:11 lab2 systemd[1]: Started Watchdog Multiplexing Daemon. So as far as I can see this part is working. -- Federico ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
Nope. Nothing more in logs. My guess is that the timeout problem generates the error. However, in reality if you run "mount", you have the target partitions mounted Therefore, I guess the problem is to understand why "dev/watchdog0 failed to set timeout" Any info needed, just ask 2013/12/21 Federico Simoncelli > - Original Message - > > From: "Pascal Jakobi" > > To: "Federico Simoncelli" , users@ovirt.org > > Sent: Friday, December 20, 2013 11:54:21 PM > > Subject: Re: [Users] AcquireHostId problem > > > > Dec 20 23:43:59 lab2 kernel: [183033.639261] softdog: Software Watchdog > > Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 > > (nowayout=0) > > Dec 20 23:44:11 lab2 systemd[1]: Starting Watchdog Multiplexing Daemon... > > Dec 20 23:44:11 lab2 wdmd[25072]: wdmd started S0 H1 G179 > > Dec 20 23:44:11 lab2 systemd-wdmd[25066]: Starting wdmd: [ OK ] > > Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 failed to set timeout > > Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 disarmed > > Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog1 armed with fire_timeout > 60 > > Dec 20 23:44:11 lab2 systemd[1]: Started Watchdog Multiplexing Daemon. > > Dec 20 23:45:33 lab2 rpc.mountd[2819]: authenticated mount request from > > 192.168.1.41:994 for /home/vdsm/data (/home/vdsm/data) > > Dec 20 23:45:39 lab2 rpc.mountd[2819]: authenticated mount request from > > 192.168.1.41:954 for /home/vdsm/data (/home/vdsm/data) > > > > Seems to work a bit. > > However I still get "unable to attach storage" when creating a domain > > It is probably a different error now. Anything interesting in vdsm.log? > > -- > Federico > -- *Pascal Jakobi* 116 rue de Stalingrad 93100 Montreuil, France *+33 6 87 47 58 19*pascal.jak...@gmail.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
- Original Message - > From: "Pascal Jakobi" > To: "Federico Simoncelli" , users@ovirt.org > Sent: Friday, December 20, 2013 11:54:21 PM > Subject: Re: [Users] AcquireHostId problem > > Dec 20 23:43:59 lab2 kernel: [183033.639261] softdog: Software Watchdog > Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 > (nowayout=0) > Dec 20 23:44:11 lab2 systemd[1]: Starting Watchdog Multiplexing Daemon... > Dec 20 23:44:11 lab2 wdmd[25072]: wdmd started S0 H1 G179 > Dec 20 23:44:11 lab2 systemd-wdmd[25066]: Starting wdmd: [ OK ] > Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 failed to set timeout > Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 disarmed > Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog1 armed with fire_timeout 60 > Dec 20 23:44:11 lab2 systemd[1]: Started Watchdog Multiplexing Daemon. > Dec 20 23:45:33 lab2 rpc.mountd[2819]: authenticated mount request from > 192.168.1.41:994 for /home/vdsm/data (/home/vdsm/data) > Dec 20 23:45:39 lab2 rpc.mountd[2819]: authenticated mount request from > 192.168.1.41:954 for /home/vdsm/data (/home/vdsm/data) > > Seems to work a bit. > However I still get "unable to attach storage" when creating a domain It is probably a different error now. Anything interesting in vdsm.log? -- Federico ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
Dec 20 23:43:59 lab2 kernel: [183033.639261] softdog: Software Watchdog Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0) Dec 20 23:44:11 lab2 systemd[1]: Starting Watchdog Multiplexing Daemon... Dec 20 23:44:11 lab2 wdmd[25072]: wdmd started S0 H1 G179 Dec 20 23:44:11 lab2 systemd-wdmd[25066]: Starting wdmd: [ OK ] Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 failed to set timeout Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 disarmed Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog1 armed with fire_timeout 60 Dec 20 23:44:11 lab2 systemd[1]: Started Watchdog Multiplexing Daemon. Dec 20 23:45:33 lab2 rpc.mountd[2819]: authenticated mount request from 192.168.1.41:994 for /home/vdsm/data (/home/vdsm/data) Dec 20 23:45:39 lab2 rpc.mountd[2819]: authenticated mount request from 192.168.1.41:954 for /home/vdsm/data (/home/vdsm/data) Seems to work a bit. However I still get "unable to attach storage" when creating a domain 2013/12/20 Federico Simoncelli > - Original Message - > > From: "Pascal Jakobi" > > To: "Federico Simoncelli" > > Sent: Friday, December 20, 2013 4:44:56 PM > > Subject: Re: [Users] AcquireHostId problem > > > > *Bug 1045512 created* < > https://bugzilla.redhat.com/show_bug.cgi?id=1045512> > > It looks perfect. Thanks. > > -- > Federico > -- *Pascal Jakobi* 116 rue de Stalingrad 93100 Montreuil, France *+33 6 87 47 58 19*pascal.jak...@gmail.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
- Original Message - > From: "Pascal Jakobi" > To: "Federico Simoncelli" > Cc: users@ovirt.org, "David Teigland" > Sent: Friday, December 20, 2013 7:19:52 AM > Subject: Re: [Users] AcquireHostId problem > > Here you go ! > I am running F19 on a Lenovo S30. > Thxs Thanks, can you open a bug on this issue? (Attach also the files to the bug). I suppose it will be later split into different ones, one for the failing watchdog device and maybe an RFE to wdmd to automatically load the softdog if there are no usable watchdog devices. -- Federico ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
- Original Message - > From: "Pascal Jakobi" > To: "Federico Simoncelli" > Cc: users@ovirt.org > Sent: Thursday, December 19, 2013 5:17:59 PM > Subject: Re: [Users] AcquireHostId problem > > 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 ? 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 can use: http://www.freedesktop.org/software/systemd/man/modules-load.d.html and for centos/rhel 6 you can look at the content of: /etc/sysconfig/modules 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 # lsmod Thanks, -- Federico ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
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 > - Original Message - > > From: "Pascal Jakobi" > > To: "Federico Simoncelli" > > 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.jak...@gmail.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
- Original Message - > From: "Pascal Jakobi" > To: "Federico Simoncelli" > 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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 ? 2013/12/19 Federico Simoncelli > - Original Message - > > From: "Pascal Jakobi" > > 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.jak...@gmail.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
- Original Message - > From: "Pascal Jakobi" > 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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
2013/12/18 Pascal Jakobi
> Apologies for not replying more quickly - I was cross-checking.
> The bad news is that it has not been resolved.
>
> I can mount NFS shares outside of ovirt. But I fail creating domains
>
> Thxs
>
>
> 2013/12/17 Itamar Heim
>
>> On 12/11/2013 03:57 AM, Pascal Jakobi wrote:
>>
>>> Context :
>>> vdsm-4.13.0-11.fc19.x86_64
>>> sanlock-2.8-1.fc19.x86_64
>>>
>>> Creating storage domain (NFS) fails with error in engine.log such as
>>> Error code AcquireHostIdFailure and error message VDSGenericException:
>>> VDSErrorException: Failed to CreateStorage
>>> And
>>> Cannot acquire host id: ('b4f05e3e-d714-45c4-adf9-8d269418338f',
>>> SanlockException(-203, 'Sanlock lockspace add failure', 'Sanlock
>>> exception'))
>>>
>>> Reading the mail archive, I can see that this is a know issue but I do
>>> not see the workaround. Can someone enlight me ?
>>>
>>> Also, is there somewhere a coherent instruction set in order to make
>>> NFSv3 work (including iptables settings). I had to stop iptables to
>>> unblock myself...
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>> hi pascal,
>>
>> was this resolved?
>>
>> thanks,
>>Itamar
>>
>
>
>
> --
> *Pascal Jakobi*
> 116 rue de Stalingrad
> 93100 Montreuil, France
>
> *+33 6 87 47 58 19 <%2B33%206%2087%2047%2058%2019>*pascal.jak...@gmail.com
>
--
*Pascal Jakobi*
116 rue de Stalingrad
93100 Montreuil, France
*+33 6 87 47 58 19*pascal.jak...@gmail.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] AcquireHostId problem
On 12/11/2013 03:57 AM, Pascal Jakobi wrote:
Context :
vdsm-4.13.0-11.fc19.x86_64
sanlock-2.8-1.fc19.x86_64
Creating storage domain (NFS) fails with error in engine.log such as
Error code AcquireHostIdFailure and error message VDSGenericException:
VDSErrorException: Failed to CreateStorage
And
Cannot acquire host id: ('b4f05e3e-d714-45c4-adf9-8d269418338f',
SanlockException(-203, 'Sanlock lockspace add failure', 'Sanlock
exception'))
Reading the mail archive, I can see that this is a know issue but I do
not see the workaround. Can someone enlight me ?
Also, is there somewhere a coherent instruction set in order to make
NFSv3 work (including iptables settings). I had to stop iptables to
unblock myself...
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
hi pascal,
was this resolved?
thanks,
Itamar
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[Users] AcquireHostId problem
Context :
vdsm-4.13.0-11.fc19.x86_64
sanlock-2.8-1.fc19.x86_64
Creating storage domain (NFS) fails with error in engine.log such as
Error code AcquireHostIdFailure and error message VDSGenericException:
VDSErrorException: Failed to CreateStorage
And
Cannot acquire host id: ('b4f05e3e-d714-45c4-adf9-8d269418338f',
SanlockException(-203, 'Sanlock lockspace add failure', 'Sanlock
exception'))
Reading the mail archive, I can see that this is a know issue but I do not
see the workaround. Can someone enlight me ?
Also, is there somewhere a coherent instruction set in order to make NFSv3
work (including iptables settings). I had to stop iptables to unblock
myself...
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
