<font size=2 face="sans-serif">Greetings,</font>
<br>
<br><font size=2 face="sans-serif">we have a problem, that the ping daemon
dies for no reason and we can't find why this happened. </font>
<br>
<br><font size=2 face="sans-serif">we use following versions on SLES 11.1:</font>
<br>
<br><font size=2 face="sans-serif">libpacemaker3-1.1.2-0.6.1</font>
<br><font size=2 face="sans-serif">pacemaker-mgmt-2.0.0-0.3.10</font>
<br><font size=2 face="sans-serif">pacemaker-mgmt-client-2.0.0-0.3.10</font>
<br><font size=2 face="sans-serif">drbd-pacemaker-8.3.8.1-0.2.9</font>
<br><font size=2 face="sans-serif">libpacemaker-devel-1.1.2-0.6.1</font>
<br><font size=2 face="sans-serif">pacemaker-1.1.2-0.6.1</font>
<br><font size=2 face="sans-serif">pacemaker-mgmt-devel-2.0.0-0.3.10</font>
<br><font size=2 face="sans-serif">libcorosync4-1.2.6-0.2.2</font>
<br><font size=2 face="sans-serif">corosync-1.2.6-0.2.2</font>
<br><font size=2 face="sans-serif">libcorosync-devel-1.2.6-0.2.2</font>
<br>
<br><font size=2 face="sans-serif"><b>here is the important part of the
log trace: </b></font>
<br><font size=2 face="sans-serif">"</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:30 node2 lrmd: [5990]:
info: rsc:OSR_IP:46535: monitor</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:30 node2 lrmd: [5990]:
info: rsc:Cluster_IP:46533: monitor</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:33 node2 lrmd: [5990]:
WARN: pingd:0:monitor process (PID 23937) timed out (try 1). Killing
with signal SIGTERM (15).</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:33 node2 lrmd: [5990]:
WARN: operation monitor[48559] on ocf::ping::pingd:0 for client 5993, its
parameters: CRM_meta_clone=[0] host_list=[xxx.xxx.xxx.xxx] CRM_meta_clone_node_max=[1]
CRM_meta_clone_max=[2] CRM_meta_notify=[false] dampen=[5s] CRM_meta_globally_unique=[false]
crm_feature_set=[3.0.2] multiplier=[100] CRM_meta_name=[monitor] CRM_meta_interval=[15000]
CRM_meta_timeout=[5000] : pid [23937] timed out</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:33 node2 crmd: [5993]:
ERROR: process_lrm_event: LRM operation pingd:0_monitor_15000 (48559) Timed
Out (timeout=5000ms)</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:33 node2 crmd: [5993]:
WARN: update_failcount: Updating failcount for pingd:0 on node2 after failed
monitor: rc=-2 (update=value++, time=1294213233)</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:35 node2 pengine:
[5992]: notice: unpack_config: On loss of CCM Quorum: Ignore</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:35 node2 pengine:
[5992]: WARN: unpack_rsc_op: Processing failed op drbd_r0:1_promote_0 on
node1: unknown exec error (-2)</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:35 node2 pengine:
[5992]: WARN: unpack_rsc_op: Processing failed op pingd:0_monitor_15000
on node2: unknown exec error (-2)</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:35 node2 pengine:
[5992]: notice: clone_print: Clone Set: pingdclone [pingd]</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:35 node2 pengine:
[5992]: notice: native_print: pingd:0
(ocf::pacemaker:ping): Started
node2 FAILED</font>
<br><font size=2 face="sans-serif">Jan 5 08:40:35 node2 pengine:
[5992]: notice: short_print: Started: [ node1 ]"</font>
<br>
<br><font size=2 face="sans-serif"><b>the ressource is configured in following
way</b>:</font>
<br><font size=2 face="sans-serif"><clone id="pingdclone"></font>
<br><font size=2 face="sans-serif"> <meta_attributes
id="pingdclone-meta_attributes"></font>
<br><font size=2 face="sans-serif"> <nvpair
id="pingdclone-meta_attributes-globally-unique" name="globally-unique"
value="false"/></font>
<br><font size=2 face="sans-serif"> </meta_attributes></font>
<br><font size=2 face="sans-serif"> <primitive
class="ocf" id="pingd" provider="pacemaker"
type="ping"></font>
<br><font size=2 face="sans-serif"> <instance_attributes
id="pingd-instance_attributes"></font>
<br><font size=2 face="sans-serif">
<nvpair id="pingd-instance_attributes-host_list" name="host_list"
value="xxx.xxx.xxx.xxx"/></font>
<br><font size=2 face="sans-serif">
<nvpair id="pingd-instance_attributes-multiplier" name="multiplier"
value="100"/></font>
<br><font size=2 face="sans-serif">
<nvpair id="nvpair-96877c9e-2825-4d7d-997b-944652f89584" name="dampen"
value="5s"/></font>
<br><font size=2 face="sans-serif"> </instance_attributes></font>
<br><font size=2 face="sans-serif"> <operations></font>
<br><font size=2 face="sans-serif">
<op id="pingd-monitor-15s" interval="15s" name="monitor"
timeout="5s"/></font>
<br><font size=2 face="sans-serif"> </operations></font>
<br><font size=2 face="sans-serif"> </primitive></font>
<br><font size=2 face="sans-serif"> </clone></font>
<br>
<br><font size=2 face="sans-serif">thx for your help in advance.</font>
<br><font size=2 face="sans-serif"><br>
</font><font size=2 color=#5f5f5f face="sans-serif">Mit freundlichen Grüßen
/ Best Regards<br>
<b><br>
Patrik Rapposch, BSc</b><br>
System Administration<br>
<b><br>
KNAPP Systemintegration GmbH</b><br>
Waltenbachstraße 9<br>
8700 Leoben, Austria <br>
Phone: +43 3842 805-915<br>
Fax: +43 3842 82930-500<br>
patrik.rapposch@knapp.com <br>
</font><a href=www.KNAPP.com><font size=2 color=#5f5f5f face="sans-serif">www.KNAPP.com</font></a><font size=2 color=#5f5f5f face="sans-serif">
<br>
<br>
Commercial register number: FN 138870x<br>
Commercial register court: Leoben</font><font size=2 face="sans-serif"><br>
</font><font size=1 color=#d2d2d2 face="sans-serif"><br>
The information in this e-mail (including any attachment) is confidential
and intended to be for the use of the addressee(s) only. If you have received
the e-mail by mistake, any disclosure, copy, distribution or use of the
contents of the e-mail is prohibited, and you must delete the e-mail from
your system. As e-mail can be changed electronically KNAPP assumes no responsibility
for any alteration to this e-mail or its attachments. KNAPP has taken every
reasonable precaution to ensure that any attachment to this e-mail has
been swept for virus. However, KNAPP does not accept any liability for
damage sustained as a result of such attachment being virus infected and
strongly recommend that you carry out your own virus check before opening
any attachment.</font>