[Pacemaker] Pacemaker with Xen 4.3 problem

[Tobias Reineck]

Hello,

I try to build a XEN HA cluster with pacemaker/corosync.
Xen 4.3 works on all nodes and also the xen live migration works fine.
Pacemaker also works with the cluster virtual IP. 
But when I try to create a XEN OCF Heartbeat resource to get online, an error
appears:

######################
Failed actions:
xen_dns_ha_start_0 on xen01.domain.dom 'unknown error' (1): call=31, status=complete, last-rc-change='Sun Jul 6 15:02:25 2014', queued=0ms, exec=555ms
xen_dns_ha_start_0 on xen02.domain.dom 'unknown error' (1): call=10, status=complete, last-rc-change='Sun Jul 6 15:15:09 2014', queued=0ms, exec=706ms
######################

I added the resource with the command

crm configure primitive xen_dns_ha ocf:heartbeat:Xen \
params xmfile="/root/xen_storage/dns_dhcp/dns_dhcp.xen" \
op monitor interval="10s" \
op start interval="0s" timeout="30s" \
op stop interval="0s" timeout="300s"

in the /var/log/messages the following error is printed:
2014-07-08T21:09:19.885239+02:00 xen01 lrmd[3443]:   notice: operation_finished: xen_dns_ha_stop_0:18214:stderr [ Error: Unable to connect to xend: No such file or directory. Is xend running? ]

I use xen 4.3 with XL toolstack without xend .
Is it possible to use pacemaker with Xen 4.3 ?
Can anybody please help me ?

Best regards
T. Reineck


 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140708/b6a32860/attachment-0003.html>