<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hello,<br><br>here the log output<br>#############################################################################################################################<br>2014-07-09T10:49:01.315764+02:00 xen01 crmd[31294]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log<br>2014-07-09T10:49:01.479820+02:00 xen01 crm_verify[31299]: notice: crm_log_args: Invoked: crm_verify -V -p<br>2014-07-09T10:49:17.135725+02:00 xen01 crmd[31359]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log<br>2014-07-09T10:49:32.683094+02:00 xen01 crmd[31367]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log<br>2014-07-09T10:52:33.063416+02:00 xen01 crmd[31668]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log<br>2014-07-09T10:52:33.224051+02:00 xen01 crm_verify[31673]: notice: crm_log_args: Invoked: crm_verify -V -p<br>2014-07-09T10:52:33.378325+02:00 xen01 pengine[31686]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log<br>2014-07-09T10:52:33.466427+02:00 xen01 crmd[3446]: notice: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_FSA_INTERNAL origin=abort_transition_graph ]<br>2014-07-09T10:52:33.480118+02:00 xen01 pengine[3445]: notice: unpack_config: On loss of CCM Quorum: Ignore<br>2014-07-09T10:52:33.480151+02:00 xen01 pengine[3445]: notice: LogActions: Start dnsdhcp#011(xen02.domain.dom)<br>2014-07-09T10:52:33.480161+02:00 xen01 pengine[3445]: notice: process_pe_message: Calculated Transition 227: /var/lib/pacemaker/pengine/pe-input-240.bz2<br>2014-07-09T10:52:33.480431+02:00 xen01 crmd[3446]: notice: te_rsc_command: Initiating action 7: monitor dnsdhcp_monitor_0 on xen02.domain.dom<br>2014-07-09T10:52:33.481059+02:00 xen01 crmd[3446]: notice: te_rsc_command: Initiating action 5: monitor dnsdhcp_monitor_0 on xen01.domain.dom (local)<br>2014-07-09T10:52:33.586987+02:00 xen01 crmd[3446]: notice: process_lrm_event: Operation dnsdhcp_monitor_0: not running (node=xen01.domain.dom, call=102, rc=7, cib-update=380, confirmed=true)<br>2014-07-09T10:52:33.611876+02:00 xen01 crmd[3446]: notice: te_rsc_command: Initiating action 4: probe_complete probe_complete-xen01.domain.dom on xen01.domain.dom (local) - no waiting<br>2014-07-09T10:52:33.810913+02:00 xen01 crmd[3446]: notice: te_rsc_command: Initiating action 6: probe_complete probe_complete-xen02.domain.dom on xen02.domain.dom - no waiting<br>2014-07-09T10:52:33.813788+02:00 xen01 crmd[3446]: notice: te_rsc_command: Initiating action 10: start dnsdhcp_start_0 on xen02.domain.dom<br>2014-07-09T10:52:33.975340+02:00 xen01 crmd[3446]: warning: status_from_rc: Action 10 (dnsdhcp_start_0) on xen02.domain.dom failed (target: 0 vs. rc: 1): Error<br>2014-07-09T10:52:33.975412+02:00 xen01 crmd[3446]: warning: update_failcount: Updating failcount for dnsdhcp on xen02.domain.dom after failed start: rc=1 (update=INFINITY, time=1404895953)<br>2014-07-09T10:52:33.979271+02:00 xen01 crmd[3446]: notice: abort_transition_graph: Transition aborted by dnsdhcp_start_0 'modify' on xen02.domain.dom: Event failed (magic=0:1;10:227:0:37f37c0c-b063-4225-a380-a41137f7d460, cib=0.94.3, source=match_graph_event:344, 0)<br>2014-07-09T10:52:33.984242+02:00 xen01 crmd[3446]: warning: update_failcount: Updating failcount for dnsdhcp on xen02.domain.dom after failed start: rc=1 (update=INFINITY, time=1404895953)<br>2014-07-09T10:52:33.985790+02:00 xen01 crmd[3446]: warning: status_from_rc: Action 10 (dnsdhcp_start_0) on xen02.domain.dom failed (target: 0 vs. rc: 1): Error<br>2014-07-09T10:52:33.987069+02:00 xen01 crmd[3446]: warning: update_failcount: Updating failcount for dnsdhcp on xen02.domain.dom after failed start: rc=1 (update=INFINITY, time=1404895953)<br>2014-07-09T10:52:33.988034+02:00 xen01 crmd[3446]: warning: update_failcount: Updating failcount for dnsdhcp on xen02.domain.dom after failed start: rc=1 (update=INFINITY, time=1404895953)<br>2014-07-09T10:52:33.988729+02:00 xen01 crmd[3446]: notice: run_graph: Transition 227 (Complete=6, Pending=0, Fired=0, Skipped=1, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-240.bz2): Stopped<br>2014-07-09T10:52:33.989334+02:00 xen01 pengine[3445]: notice: unpack_config: On loss of CCM Quorum: Ignore<br>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)<br>2014-07-09T10:52:33.990615+02:00 xen01 pengine[3445]: warning: unpack_rsc_op_failure: Processing failed op start for dnsdhcp on xen02.domain.dom: unknown error (1)<br>2014-07-09T10:52:33.991355+02:00 xen01 pengine[3445]: notice: LogActions: Recover dnsdhcp#011(Started xen02.domain.dom)<br>2014-07-09T10:52:33.992005+02:00 xen01 pengine[3445]: notice: process_pe_message: Calculated Transition 228: /var/lib/pacemaker/pengine/pe-input-241.bz2<br>2014-07-09T10:52:34.040477+02:00 xen01 pengine[3445]: notice: unpack_config: On loss of CCM Quorum: Ignore<br>2014-07-09T10:52:34.042715+02:00 xen01 pengine[3445]: warning: unpack_rsc_op_failure: Processing failed op start for dnsdhcp on xen02.domain.dom: unknown error (1)<br>2014-07-09T10:52:34.044920+02:00 xen01 pengine[3445]: warning: unpack_rsc_op_failure: Processing failed op start for dnsdhcp on xen02.domain.dom: unknown error (1)<br>2014-07-09T10:52:34.047177+02:00 xen01 pengine[3445]: warning: common_apply_stickiness: Forcing dnsdhcp away from xen02.domain.dom after 1000000 failures (max=1000000)<br>2014-07-09T10:52:34.049493+02:00 xen01 pengine[3445]: notice: LogActions: Recover dnsdhcp#011(Started xen02.domain.dom -> xen01.domain.dom)<br>2014-07-09T10:52:34.051670+02:00 xen01 crmd[3446]: notice: te_rsc_command: Initiating action 2: stop dnsdhcp_stop_0 on xen02.domain.dom<br>2014-07-09T10:52:34.054610+02:00 xen01 pengine[3445]: notice: process_pe_message: Calculated Transition 229: /var/lib/pacemaker/pengine/pe-input-242.bz2<br>2014-07-09T10:52:39.566582+02:00 xen01 crmd[3446]: notice: te_rsc_command: Initiating action 9: start dnsdhcp_start_0 on xen01.domain.dom (local)<br>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 '[' ]<br>2014-07-09T10:52:39.680299+02:00 xen01 lrmd[3443]: notice: operation_finished: dnsdhcp_start_0:31734:stderr [ Failed to parse config: Invalid argument ]<br>2014-07-09T10:52:39.719162+02:00 xen01 crmd[3446]: notice: process_lrm_event: Operation dnsdhcp_start_0: unknown error (node=xen01.domain.dom, call=103, rc=1, cib-update=384, confirmed=true)<br>2014-07-09T10:52:39.720276+02:00 xen01 crmd[3446]: notice: process_lrm_event: xen01.domain.dom-dnsdhcp_start_0:103 [ /root/xen_storage/dns_dhcp/dnsdhcp.xen:24: config parsing error near `dnsdhcp': syntax error, unexpected IDENT, expecting STRING or NUMBER or '['\nFailed to parse config: Invalid argument\n ]<br>2014-07-09T10:52:39.721666+02:00 xen01 crmd[3446]: warning: status_from_rc: Action 9 (dnsdhcp_start_0) on xen01.domain.dom failed (target: 0 vs. rc: 1): Error<br>2014-07-09T10:52:39.722533+02:00 xen01 crmd[3446]: warning: update_failcount: Updating failcount for dnsdhcp on xen01.domain.dom after failed start: rc=1 (update=INFINITY, time=1404895959)<br>2014-07-09T10:52:39.723280+02:00 xen01 attrd[3444]: notice: attrd_trigger_update: Sending flush op to all hosts for: fail-count-dnsdhcp (INFINITY)<br>2014-07-09T10:52:39.724021+02:00 xen01 attrd[3444]: notice: attrd_perform_update: Sent update 317: fail-count-dnsdhcp=INFINITY<br>2014-07-09T10:52:39.724752+02:00 xen01 attrd[3444]: notice: attrd_trigger_update: Sending flush op to all hosts for: last-failure-dnsdhcp (1404895959)<br>2014-07-09T10:52:39.725445+02:00 xen01 attrd[3444]: notice: attrd_perform_update: Sent update 319: last-failure-dnsdhcp=1404895959<br>2014-07-09T10:52:39.726159+02:00 xen01 crmd[3446]: notice: abort_transition_graph: Transition aborted by dnsdhcp_start_0 'modify' on xen01.domain.dom: Event failed (magic=0:1;9:229:0:37f37c0c-b063-4225-a380-a41137f7d460, cib=0.94.7, source=match_graph_event:344, 0)<br>2014-07-09T10:52:39.727152+02:00 xen01 crmd[3446]: warning: update_failcount: Updating failcount for dnsdhcp on xen01.domain.dom after failed start: rc=1 (update=INFINITY, time=1404895959)<br>2014-07-09T10:52:39.727872+02:00 xen01 crmd[3446]: warning: status_from_rc: Action 9 (dnsdhcp_start_0) on xen01.domain.dom failed (target: 0 vs. rc: 1): Error<br>2014-07-09T10:52:39.730441+02:00 xen01 crmd[3446]: warning: update_failcount: Updating failcount for dnsdhcp on xen01.domain.dom after failed start: rc=1 (update=INFINITY, time=1404895959)<br>2014-07-09T10:52:39.731249+02:00 xen01 crmd[3446]: warning: update_failcount: Updating failcount for dnsdhcp on xen01.domain.dom after failed start: rc=1 (update=INFINITY, time=1404895959)<br>2014-07-09T10:52:39.731907+02:00 xen01 crmd[3446]: notice: abort_transition_graph: Transition aborted by status-1-fail-count-dnsdhcp, fail-count-dnsdhcp=INFINITY: Transient attribute change (create cib=0.94.8, source=te_update_diff:391, path=/cib/status/node_state[@id='1']/transient_attributes[@id='1']/instance_attributes[@id='status-1'], 0)<br>2014-07-09T10:52:39.733108+02:00 xen01 crmd[3446]: notice: run_graph: Transition 229 (Complete=3, Pending=0, Fired=0, Skipped=1, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-242.bz2): Stopped<br>2014-07-09T10:52:39.734870+02:00 xen01 pengine[3445]: notice: unpack_config: On loss of CCM Quorum: Ignore<br>2014-07-09T10:52:39.736966+02:00 xen01 pengine[3445]: warning: unpack_rsc_op_failure: Processing failed op start for dnsdhcp on xen01.domain.dom: unknown error (1)<br>2014-07-09T10:52:39.737874+02:00 xen01 pengine[3445]: warning: unpack_rsc_op_failure: Processing failed op start for dnsdhcp on xen01.domain.dom: unknown error (1)<br>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)<br>2014-07-09T10:52:39.739491+02:00 xen01 pengine[3445]: warning: common_apply_stickiness: Forcing dnsdhcp away from xen01.domain.dom after 1000000 failures (max=1000000)<br>2014-07-09T10:52:39.740337+02:00 xen01 pengine[3445]: warning: common_apply_stickiness: Forcing dnsdhcp away from xen02.domain.dom after 1000000 failures (max=1000000)<br>2014-07-09T10:52:39.741456+02:00 xen01 pengine[3445]: notice: LogActions: Stop dnsdhcp#011(xen01.domain.dom)<br>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<br>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)<br>2014-07-09T10:52:45.211574+02:00 xen01 Xen(dnsdhcp)[31780]: INFO: Xen domain dnsdhcp already stopped.<br>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) ]<br>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)<br>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<br>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 ]<br><br>#############################################################################################################################<br><br>here the Xen VM config file:<br>#############################################################################################################################<br>builder='hvm'<br>name='dnsdhcp'<br>vcpus='1'<br>cpus='1'<br>memory='768'<br>disk=['file:/root/xen_storage/dns_dhcp/dns_dhcp.img,xvda,w']<br>vif=['type=paravirtualized, bridge=xenbr0, model=e1000, vifname=dns_dhcp, mac=00:16:3E:52:4C:38']<br>boot='c'<br>acpi='1'<br>apic='1'<br>viridian='1'<br>stdvga='0'<br>vnc='1'<br>vnclisten='0.0.0.0'<br>sdl='0'<br>usbdevice='tablet'<br>xen_platform_pci='1'<br>keymap='de'<br>on_poweroff='destroy'<br>on_reboot='restart'<br>on_crash='restart'<br>#############################################################################################################################<br><br>I dont know why pacemaker complains the:<br><br>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 '[' ]<br><br>and<br><br>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)<br><br>Best regards<br>T. Reineck<br><br><br><div><hr id="stopSpelling">Date: Wed, 9 Jul 2014 09:37:10 +0200<br>From: alxgomz@gmail.com<br>To: pacemaker@oss.clusterlabs.org<br>Subject: Re: [Pacemaker] Pacemaker with Xen 4.3 problem<br><br><div dir="ltr"><div><div><div>Actually I did it for the stonith resource agent external:xen0.<br></div>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.<br>
</div>What error do you have when using xl instead of xm?<br><br></div>Regards.<br></div><div class="ecxgmail_extra"><br><br><div class="ecxgmail_quote">2014-07-09 8:39 GMT+02:00 Tobias Reineck <span dir="ltr"><<a href="mailto:tobias.reineck@hotmail.de" target="_blank">tobias.reineck@hotmail.de</a>></span>:<br>
<blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">
<div><div dir="ltr">Hello,<br><br>do you mean the "Xen" script in /usr/lib/ocf/resource.d/heartbeat/ ?<br>I also tried this to replace all "xm" with "xl" with no success.<br>Is it possible that you can show me you RA resource for Xen ?<br>
<br>Best regards<br>T. Reineck<br><br><br><br><div><hr>Date: Tue, 8 Jul 2014 22:27:59 +0200<br>From: <a href="mailto:alxgomz@gmail.com" target="_blank">alxgomz@gmail.com</a><br>To: <a href="mailto:pacemaker@oss.clusterlabs.org" target="_blank">pacemaker@oss.clusterlabs.org</a><br>
Subject: Re: [Pacemaker] Pacemaker with Xen 4.3 problem<div><div class="h5"><br><br><p dir="ltr">IIRC the xen RA uses 'xm'. However fixing the RAin is trivial and worked for me (if you're using the same RA)</p>
<div>Le 2014-07-08 21:39, "Tobias Reineck" <<a href="mailto:tobias.reineck@hotmail.de" target="_blank">tobias.reineck@hotmail.de</a>> a écrit :<br><blockquote style="border-left:1px #ccc solid;padding-left:1ex;">
<div><div dir="ltr">Hello,<br><br>I try to build a XEN HA cluster with pacemaker/corosync.<br>Xen 4.3 works on all nodes and also the xen live migration works fine.<br>Pacemaker also works with the cluster virtual IP. <br>
But when I try to create a XEN OCF Heartbeat resource to get online, an error<br>appears:<br><br>######################<br>Failed actions:<br>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<br>
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<br>######################<br><br>I added the resource with the command<br>
<br>crm configure primitive xen_dns_ha ocf:heartbeat:Xen \<br>params xmfile="/root/xen_storage/dns_dhcp/dns_dhcp.xen" \<br>op monitor interval="10s" \<br>op start interval="0s" timeout="30s" \<br>
op stop interval="0s" timeout="300s"<br><br>in the /var/log/messages the following error is printed:<br>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? ]<br>
<br>I use xen 4.3 with XL toolstack without xend .<br>Is it possible to use pacemaker with Xen 4.3 ?<br>Can anybody please help me ?<br><br>Best regards<br>T. Reineck<br><br><br> </div></div>
<br>_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br></blockquote></div>
<br>_______________________________________________
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a></div></div></div> </div></div>
<br>_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________
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</div> </div></body>
</html>