[Pacemaker] Pacemaker with Xen 4.3 problem
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@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
Re: [Pacemaker] Pacemaker with Xen 4.3 problem
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: alxg...@gmail.com To: pacemaker@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" 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@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@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@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
Re: [Pacemaker] Pacemaker with Xen 4.3 problem
op_failure: Processing failed op start for dnsdhcp on xen01.domain.dom: unknown error (1) 2014-07-09T10:52:39.738615+02:00 xen01 pengine[3445]: warning: unpack_rsc_op_failure: Processing failed op start for dnsdhcp on xen02.domain.dom: unknown error (1) 2014-07-09T10:52:39.739491+02:00 xen01 pengine[3445]: warning: common_apply_stickiness: Forcing dnsdhcp away from xen01.domain.dom after 100 failures (max=100) 2014-07-09T10:52:39.740337+02:00 xen01 pengine[3445]: warning: common_apply_stickiness: Forcing dnsdhcp away from xen02.domain.dom after 100 failures (max=100) 2014-07-09T10:52:39.741456+02:00 xen01 pengine[3445]: notice: LogActions: Stopdnsdhcp#011(xen01.domain.dom) 2014-07-09T10:52:39.742298+02:00 xen01 pengine[3445]: notice: process_pe_message: Calculated Transition 230: /var/lib/pacemaker/pengine/pe-input-243.bz2 2014-07-09T10:52:39.743362+02:00 xen01 crmd[3446]: notice: te_rsc_command: Initiating action 2: stop dnsdhcp_stop_0 on xen01.domain.dom (local) 2014-07-09T10:52:45.211574+02:00 xen01 Xen(dnsdhcp)[31780]: INFO: Xen domain dnsdhcp already stopped. 2014-07-09T10:52:45.230365+02:00 xen01 lrmd[3443]: notice: operation_finished: dnsdhcp_stop_0:31780:stderr [ dnsdhcp is an invalid domain identifier (rc=-6) ] 2014-07-09T10:52:45.232665+02:00 xen01 crmd[3446]: notice: process_lrm_event: Operation dnsdhcp_stop_0: ok (node=xen01.domain.dom, call=104, rc=0, cib-update=386, confirmed=true) 2014-07-09T10:52:45.235199+02:00 xen01 crmd[3446]: notice: run_graph: Transition 230 (Complete=2, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-243.bz2): Complete 2014-07-09T10:52:45.236029+02:00 xen01 crmd[3446]: notice: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ] # here the Xen VM config file: # builder='hvm' name='dnsdhcp' vcpus='1' cpus='1' memory='768' disk=['file:/root/xen_storage/dns_dhcp/dns_dhcp.img,xvda,w'] vif=['type=paravirtualized, bridge=xenbr0, model=e1000, vifname=dns_dhcp, mac=00:16:3E:52:4C:38'] boot='c' acpi='1' apic='1' viridian='1' stdvga='0' vnc='1' vnclisten='0.0.0.0' sdl='0' usbdevice='tablet' xen_platform_pci='1' keymap='de' on_poweroff='destroy' on_reboot='restart' on_crash='restart' # I dont know why pacemaker complains the: 2014-07-09T10:52:39.679297+02:00 xen01 lrmd[3443]: notice: operation_finished: dnsdhcp_start_0:31734:stderr [ /root/xen_storage/dns_dhcp/dnsdhcp.xen:24: config parsing error near `dnsdhcp': syntax error, unexpected IDENT, expecting STRING or NUMBER or '[' ] and 2014-07-09T10:52:33.990014+02:00 xen01 pengine[3445]: warning: unpack_rsc_op_failure: Processing failed op start for dnsdhcp on xen02.domain.dom: unknown error (1) Best regards T. Reineck Date: Wed, 9 Jul 2014 09:37:10 +0200 From: alxg...@gmail.com To: pacemaker@oss.clusterlabs.org Subject: Re: [Pacemaker] Pacemaker with Xen 4.3 problem 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 : 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: alxg...@gmail.com To: pacemaker@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" 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:
