You hit a pingd bug. The counter wraps around pingd wasn't able to handle it.
This and the logging is fixed for the next version.
On Thu, Feb 12, 2009 at 11:33, Tim Verhoeven wrote:
> Hi,
>
> I had a strange problem with one of my clusters last night. As far as
> I can see it it seems that the p
Hi,
I had a strange problem with one of my clusters last night. As far as
I can see it it seems that the pingd fails to do successful pings
after a certain period. Here is part of the logs from 1 node of my 2
node cluster :
Feb 12 03:37:21 slave1 pingd: [4744]: info: stand_alone_ping: Node
10.0.1
