Rpm built for RHEL5: heartbeat-common-2.99.2-8.1 libheartbeat2-2.99.2-8.1 heartbeat-2.99.2-8.1 heartbeat-resources-2.99.2-8.1 pacemaker-1.0.3-2.2 pacemaker-mgmt-client-1.99.1-2.1 libpacemaker3-1.0.3-2.2 pacemaker-mgmt-1.99.1-2.1
If i start pingd manually (beside working heartbeat+pacemaker) it gives me following when in /var/log/ha-debug appears "stand_alone_ping: Node xx.yy.zz.ww is unreachable (read)": [r...@gate2]# date ;/usr/lib64/heartbeat/pingd -a pingd -d 10 -m 1000 -h xx.yy.zz.ww; date Thu Jul 23 19:25:24 CEST 2009 No error message: -1: Resource temporarily unavailable (11) No error message: -1: Resource temporarily unavailable (11) No error message: -1: Resource temporarily unavailable (11) No error message: -1: Resource temporarily unavailable (11) No error message: -1: Resource temporarily unavailable (11) No error message: -1: Resource temporarily unavailable (11) ... System ping reports no errors. Thanks, Jarek "General Linux-HA mailing list" <[email protected]> napisał(a): > version? > > On Wed, Jul 22, 2009 at 4:16 PM, <[email protected]> wrote: > > Hi All, > > > > I'm using pingd in clone mode (pacemaker). I observe lots of messages > > saying that "Node xx.yy.zz.ww is unreachable" (see at the end of this > > mail). "xx.yy.zz.ww" is IP of main router. I checked the connection using > > the system ping command. This way everything seems to be OK (see below). > > Could You tell me what causes the info in heartbeat logs? > > > > Thanks > > Jarek > > > > > > ------------------------------------------------------------- > > [r...@gate2 ~]# ping xx.yy.zz.ww > > > > ... > > 64 bytes from xx.yy.zz.ww: icmp_seq=2758 ttl=255 time=0.562 ms > > 64 bytes from xx.yy.zz.ww: icmp_seq=2759 ttl=255 time=1.18 ms > > 64 bytes from xx.yy.zz.ww: icmp_seq=2760 ttl=255 time=1.04 ms > > 64 bytes from xx.yy.zz.ww: icmp_seq=2761 ttl=255 time=0.688 ms > > 64 bytes from xx.yy.zz.ww: icmp_seq=2762 ttl=255 time=0.906 ms > > 64 bytes from xx.yy.zz.ww: icmp_seq=2763 ttl=255 time=0.556 ms > > 64 bytes from xx.yy.zz.ww: icmp_seq=2764 ttl=255 time=0.778 ms > > 64 bytes from xx.yy.zz.ww: icmp_seq=2765 ttl=255 time=1.38 ms > > 64 bytes from xx.yy.zz.ww: icmp_seq=2766 ttl=255 time=0.998 ms > > > > --- xx.yy.zz.ww ping statistics --- > > 2766 packets transmitted, 2766 received, 0% packet loss, time 2766412ms > > rtt min/avg/max/mdev = 0.414/2.818/68.540/2.944 ms > > > > ------------------------------------------------------------- > > /var/log/ha-debug > > > > pingd[4250]: 2009/07/21_15:06:55 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:06:56 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:06:59 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:07:00 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:07:01 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:07:02 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > attrd[4027]: 2009/07/21_15:07:13 info: attrd_trigger_update: Sending flush > > op to all hosts for: pingd > > attrd[4027]: 2009/07/21_15:07:13 info: attrd_ha_callback: flush message > > from gate2 > > cib[4024]: 2009/07/21_15:16:36 info: cib_stats: Processed 3 operations > > (0.00us average, 0% utilization) in the last 10min > > attrd[4027]: 2009/07/21_15:47:10 info: attrd_ha_callback: flush message > > from gate3 > > attrd[4027]: 2009/07/21_15:47:31 info: attrd_ha_callback: flush message > > from gate3 > > cib[4024]: 2009/07/21_15:56:36 info: cib_stats: Processed 6 operations > > (1666.00us average, 0% utilization) in the last 10min > > pingd[4250]: 2009/07/21_15:59:24 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:59:25 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:59:26 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:59:27 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:59:28 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:59:29 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > attrd[4027]: 2009/07/21_15:59:40 info: attrd_trigger_update: Sending flush > > op to all hosts for: pingd > > attrd[4027]: 2009/07/21_15:59:40 info: attrd_ha_callback: flush message > > from gate2 > > pingd[4250]: 2009/07/21_15:59:42 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > pingd[4250]: 2009/07/21_15:59:43 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > attrd[4027]: 2009/07/21_15:59:54 info: attrd_trigger_update: Sending flush > > op to all hosts for: pingd > > attrd[4027]: 2009/07/21_15:59:54 info: attrd_ha_callback: flush message > > from gate2 > > cib[4024]: 2009/07/21_16:06:36 info: cib_stats: Processed 6 operations > > (1666.00us average, 0% utilization) in the last 10min > > pingd[4250]: 2009/07/21_16:14:51 info: stand_alone_ping: Node xx.yy.zz.ww > > is unreachable (read) > > ... > > > > --------------------------- > > > > _______________________________________________ > > Linux-HA mailing list > > [email protected] > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > See also: http://linux-ha.org/ReportingProblems > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
