[Users] Sanlock issue when trying to start vm

[Dennis Jacobfeuerborn]

Hi,
after getting the 3.1 beta engine and a host set up I now get an error when
trying to start a vm.

Engine reports this:
VM myvm is down. Exit message: internal error Failed to open socket to
sanlock daemon: No such file or directory.

On the node no sanlock daemon is running. When I try to start the service I
get this:
Jun 19 20:22:31 node systemd-sanlock[13607]: Starting sanlock: [  OK  ]
Jun 19 20:22:31 node sanlock[13621]: 2012-06-19 20:22:31+0200 910 [13621]:
sanlock daemon started 2.3 aio 1 10 renew 20 80 host
93bea910-1d9d-4203-8333-beb3d7b92c10.node.local time 1340130151
Jun 19 20:22:31 node sanlock[13621]: 2012-06-19 20:22:31+0200 910 [13621]:
set scheduler RR|RESET_ON_FORK priority 99 failed: Operation not permitted
Jun 19 20:22:31 node sanlock[13621]: 2012-06-19 20:22:31+0200 910 [13621]:
wdmd connect failed for watchdog handling
Jun 19 20:22:31 node systemd[1]: sanlock.service: main process exited,
code=exited, status=255
Jun 19 20:22:31 node systemd[1]: Unit sanlock.service entered failed state.

I followed the SELinux and sanlock threads but I disabled SELinux on the
node so that cannot be a reason for this to fail.

Regards,
  Dennis