[Pacemaker] Pacemaker with Xen 4.3 problem

Alexandre alxgomz at gmail.com
Wed Jul 9 03:37:10 EDT 2014


Actually I did it for the stonith resource agent external:xen0.
xm and xl are supposed to be semantically very close and as far as I can
see the ocf:heartbeat:Xen agent doesn't seem to use any xm command that
shouldn't work with xl.
What error do you have when using xl instead of xm?

Regards.


2014-07-09 8:39 GMT+02:00 Tobias Reineck <tobias.reineck at hotmail.de>:

> Hello,
>
> do you mean the "Xen" script in /usr/lib/ocf/resource.d/heartbeat/ ?
> I also tried this to replace all "xm" with "xl" with no success.
> Is it possible that you can show me you RA resource for Xen ?
>
> Best regards
> T. Reineck
>
>
>
> ------------------------------
> Date: Tue, 8 Jul 2014 22:27:59 +0200
> From: alxgomz at gmail.com
> To: pacemaker at oss.clusterlabs.org
> Subject: Re: [Pacemaker] Pacemaker with Xen 4.3 problem
>
>
> IIRC the xen RA uses 'xm'. However fixing the RAin is trivial and worked
> for me (if you're using the same RA)
> Le 2014-07-08 21:39, "Tobias Reineck" <tobias.reineck at hotmail.de> a écrit
> :
>
> 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
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
>
> _______________________________________________ Pacemaker mailing list:
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home:
> http://www.clusterlabs.org Getting started:
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs:
> http://bugs.clusterlabs.org
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140709/6423278a/attachment-0003.html>


More information about the Pacemaker mailing list