[Pacemaker] Reduce log level of retrying messages from pingd

[Junko IKEDA]

Hi,

I set up two pingd RAs on the same nodes using Pacemaker 1.0.12.
Each pingd has the other destination.

property \
        no-quorum-policy="ignore" \
        stonith-enabled="false" \
        startup-fencing="false" \
        crmd-transition-delay="2s"

rsc_defaults \
        resource-stickiness="INFINITY" \
        migration-threshold="1"

clone clnPingd01 pingd01

primitive pingd01 ocf:pacemaker:pingd \
        params name="default_ping_set01" host_list="192.168.201.254"
multiplier="100" \
        op start   interval="0s" timeout="100s" on-fail="restart" \
        op monitor interval="2s" timeout="100s" on-fail="restart" \
        op stop    interval="0s" timeout="100s" on-fail="ignore"

clone clnPingd02 pingd02

primitive pingd02 ocf:pacemaker:pingd \
        params name="default_ping_set02" host_list="192.168.133.11"
multiplier="100"  \
        op start   interval="0s" timeout="100s" on-fail="restart" \
        op monitor interval="2s" timeout="100s" on-fail="restart" \
        op stop    interval="0s" timeout="100s" on-fail="ignore"


During their execution, it seems that each pingd receives the all of
the ICMP pacekets including the other destination's one.
It means "pingd01" can receive "ECHO REPLY " from "pingd02" and the
opposite is also true.
pingd says "Retrying..." each time when it receives the other's ICMP packets.
(see attached: hb_report\node02\ha-log.txt)

Jul 24 11:09:14 node02 crmd: [2364]: info: do_state_transition: State
transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS
cause=C_FSA_INTERNAL origin=notify_crmd ]
Jul 24 11:09:14 node02 crmd: [2364]: info: do_state_transition:
Starting PEngine Recheck Timer
Jul 24 11:09:14 node02 pengine: [2369]: info: process_pe_message:
Transition 2: PEngine Input stored in: /var/lib/pengine/pe-input-2.bz2
Jul 24 11:09:16 node02 pingd: [2390]: info: ping_read: Retrying...
Jul 24 11:09:18 node02 attrd: [2363]: info: attrd_ha_callback: flush
message from node01
Jul 24 11:09:18 node02 attrd: [2363]: info: attrd_ha_callback: flush
message from node01
Jul 24 11:09:23 node02 pingd: [2390]: info: ping_read: Retrying...
Jul 24 11:09:30 node02 pingd: [2390]: info: ping_read: Retrying...
Jul 24 11:09:31 node02 pingd: [2390]: info: ping_read: Retrying...
Jul 24 11:09:38 node02 pingd: [2390]: info: ping_read: Retrying...
Jul 24 11:09:39 node02 pingd: [2390]: info: ping_read: Retrying...
Jul 24 11:09:49 node02 pingd: [2390]: info: ping_read: Retrying...

It's just a little annoying.
This log message is enough when the debug mode is on, doesn't it?
I sent pull request to Pacemaker 1.0's repo,  please check it.
https://github.com/ClusterLabs/pacemaker-1.0/pull/6


Regards,
Junko IKEDA

NTT DATA INTELLILINK CORPORATION
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hb_report.tar.bz2
Type: application/x-bzip2
Size: 33371 bytes
Desc: not available
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120724/835903c6/attachment-0002.bz2>