<div dir="ltr">Hi,<div><br></div><div>I've seen I made a mistake with <span style="font-size:12.8000001907349px">-INFINITY, I confuse something, so you can ignore the part I'm talking about -INFINITY. </span></div><div><span style="font-size:12.8000001907349px">I saw I specified this with "-inf"</span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">Thanks</span></div><div><span style="font-size:12.8000001907349px">Oscar</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-15 10:43 GMT+02:00 Oscar Salvador <span dir="ltr"><<a href="mailto:osalvador.vilardaga@gmail.com" target="_blank">osalvador.vilardaga@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi!<div><br></div><div>I have a problem with fencing.</div><div>I'm using fence-agents, and a configured a one that uses libvirt device.</div><div><br></div><div>Versions:</div><div><br></div><div>fence-agents 4.0.18<br></div><div>corosync 2.3.4<br></div><div>pacemaker 1.1.12<br></div><div><br></div><div>Here is the configuration:</div><div><br></div><div><div>node 1053402612: server01</div><div>node 1053402613: server02</div><div>primitive IP-rsc_nginx IPaddr2 \</div><div> params ip=xx.xx.xx.xx nic=eth0 cidr_netmask=xx.xx.xx.xx \</div><div> meta migration-threshold=2 \</div><div> op monitor interval=20 timeout=60 on-fail=restart</div><div>primitive Nginx-rsc nginx \</div><div> meta migration-threshold=2 \</div><div> op monitor interval=20 timeout=60 on-fail=restart</div><div>primitive p_fence_server01 stonith:external/libvirt \</div><div> params hostlist=server01 hypervisor_uri="qemu+tcp://virtnode01/system" \</div><div> op monitor interval=60</div><div>primitive p_fence_server02 stonith:external/libvirt \</div><div> params hostlist=server02 hypervisor_uri="qemu+tcp://virtnode02/system" \</div><div> op monitor interval=60</div><div>location l_fence_server01 p_fence_server01 -inf: server01</div><div>location l_fence_server02 p_fence_server02 -inf: server02</div><div>colocation lb-loc inf: IP-rsc_nginx Nginx-rsc</div><div>order lb-ord inf: IP-rsc_nginx Nginx-rsc</div><div>property cib-bootstrap-options: \</div><div> stonith-enabled=true \</div><div> no-quorum-policy=ignore \</div><div> default-resource-stickiness=100 \</div><div> dc-version=1.1.12-561c4cf \</div><div> cluster-infrastructure=corosync</div></div><div><br></div><div><br></div><div>Whe I commit the conf, I can see the followning in the logs:</div><div><br></div><div>First: </div><div><br></div><div><i>Jun 15 10:16:05 [27835] server02 stonithd: info: cib_device_update: Device p_fence_server02 has been disabled on server02: score=-INFINITY</i><br></div><div><br></div><div>Since I specifed a location with:</div><div><br></div><div>"<i>location l_fence_server02 p_fence_server02 -inf: server02</i>"</div><div><br></div><div>Why it put an -INFINITY score? It is the default behaviour? As far as I know, -INFINITY means "not run this resource on this node".</div><div><br></div><div>Then I receive:</div><div><br></div><div><i>Jun 15 10:16:05 [27835] server02 stonithd: info: xml_patch_version_check: Current num_updates is too high (8 > 7)<br></i></div><div><i><br></i></div><div><div><i>Jun 15 10:16:07 server02 stonith: [30410]: WARN: external_status: 'libvirt status' failed with rc 1</i></div><div><i>Jun 15 10:16:07 server02 stonith: [30410]: ERROR: external/libvirt device not accessible.</i></div><div><i>Jun 15 10:16:07 [27835] server02 stonithd: info: internal_stonith_action_execute: Attempt 2 to execute fence_legacy (monitor). remaining timeout is 19</i></div><div><i>Jun 15 10:16:09 server02 stonith: [30435]: WARN: external_status: 'libvirt status' failed with rc 1</i></div><div><i>Jun 15 10:16:09 server02 stonith: [30435]: ERROR: external/libvirt device not accessible.</i></div></div><div><i><br></i></div><div><i><br></i></div><div><div><i>Jun 15 10:16:09 [27835] server02 stonithd: info: update_remaining_timeout: Attempted to execute agent fence_legacy (monitor) the maximum number of times (2) allowed </i></div><div><i>Jun 15 10:16:09 [27835] server02 stonithd: notice: log_operation: Operation 'monitor' [30434] for device 'p_fence_server01' returned: -201 (Generic Pacemaker error)</i></div><div><i>Jun 15 10:16:09 [27835] server02 stonithd: warning: log_operation: p_fence_server01:30434 [ Performing: stonith -t external/libvirt -S ]</i></div><div><i>Jun 15 10:16:09 [27835] server02 stonithd: warning: log_operation: p_fence_server01:30434 [ failed: 1 ]</i></div></div><div><br></div><div><br></div><div>One think it called my attention was:</div><div><br></div><div>"Performing: stonith -t external/libvirt -S"</div><div><br></div><div>If I execute this command, I receive:</div><div><br></div><div><div><i># stonith -t external/libvirt -S</i></div><div><i>Must specify either -p option, -F option, -E option, or name=value style arguments</i></div><div><i>usage:</i></div><div><i><span style="white-space:pre-wrap"> </span> stonith [-svh] -L</i></div><div><i><span style="white-space:pre-wrap"> </span> stonith [-svh] -t stonith-device-type -n</i></div><div><i><span style="white-space:pre-wrap"> </span> stonith [-svh] -t stonith-device-type -m</i></div><div><i><span style="white-space:pre-wrap"> </span> stonith [-svh] -t stonith-device-type {-p stonith-device-parameters | -F stonith-device-parameters-file | -E | name=value...} [-c count] -lS</i></div><div><i><span style="white-space:pre-wrap"> </span> stonith [-svh] -t stonith-device-type {-p stonith-device-parameters | -F stonith-device-parameters-file | -E | name=value...} [-c count] -T {reset|on|off} nodename</i></div><div><i><br></i></div><div><i>where:</i></div><div><i><span style="white-space:pre-wrap"> </span>-L<span style="white-space:pre-wrap"> </span>list supported stonith device types</i></div><div><i><span style="white-space:pre-wrap"> </span>-l<span style="white-space:pre-wrap"> </span>list hosts controlled by this stonith device</i></div><div><i><span style="white-space:pre-wrap"> </span>-S<span style="white-space:pre-wrap"> </span>report stonith device status</i></div><div><i><span style="white-space:pre-wrap"> </span>-s<span style="white-space:pre-wrap"> </span>silent</i></div><div><i><span style="white-space:pre-wrap"> </span>-v<span style="white-space:pre-wrap"> </span>verbose</i></div><div><i><span style="white-space:pre-wrap"> </span>-n<span style="white-space:pre-wrap"> </span>output the config names of stonith-device-parameters</i></div><div><i><span style="white-space:pre-wrap"> </span>-m<span style="white-space:pre-wrap"> </span>display meta-data of the stonith device type</i></div><div><i><span style="white-space:pre-wrap"> </span>-h<span style="white-space:pre-wrap"> </span>display detailed help message with stonith device description(s)</i></div></div><div><br></div><div><br></div><div>Si, it seems that it is executed with some missing parameters.</div><div><br></div><div>Anyone has an idea?</div><div><br></div><div>Thank you very much in advance</div><span class="HOEnZb"><font color="#888888"><div>Oscar</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></font></span></div>
</blockquote></div><br></div>