[Linux-HA] Intercommunication between heartbeat processes problem

[Varun Menghani]

Hi,
I had encountered a similar problem when I was running 2 clusters in a
single network. Apparently the heartbeat messages were getting mixed up
among the 2 clusters.
The above problem was solved using cluster keys - by assigning a unique
key per cluster so that each cluster reads only its own messages - they
can be defined in the authkeys file.
Hope this helps.
Regards,
Varun.


On Sat, 2006-03-11 at 05:42, Guochun Shi wrote:
> Héctor Cordobés wrote:
> 
> > Hi all
> >
> > I am using heartbeat 2.0.2 (on v1 scheme), and I am finding a problem 
> > during some stress tests I am making on the cluster. From time to time 
> > I find these two errors (separately) after issuing some restarts:
> >
> > HBDoMsg_T_ACK: corrupted ackseq current hiseq = 510 ackseq =550 in 
> > this message
> >
> Each message has a seq number, this message says we have sent out 510 
> messessages but we are now receiving ACK message for message 550.
> This is impossible because we have not sent out message 550 yet, that's 
> why it complains.
> 
> > heartbeat: [2407]: ERROR: should_drop_message: attempted replay attack 
> > [host1]? [gen = 16, curgen = 62]
> >
> The current generation number is 62 based on previous messages, and we 
> are now receiving a message with generation number 16,
> and that is considered a replay attack.
> Every time you restart heartbeat, generation number is increased by one, 
> you can see the current generation number for local node in 
> /var/lib/heartbeat/hb_generation
> 
> I am not sure how these problem happened, a full logfile/debugfile will 
> help.
> 
> -Guochun
> 
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
-- 
Varun Menghani <varun.menghani at airtightnetworks.net>
Airtight Networks
----

“THE INFORMATION IN THIS EMAIL AND ANY ATTACHMENTS IS CONFIDENTIAL AND
INTENDED SOLELY FOR THE USE OF THE PERSON NAMED ABOVE.  IF YOU ARE NOT
THE INTENDED RECIPIENT, OR HAVE OTHERWISE RECEIVED THIS EMAIL IN ERROR,
DO NOT READ, DISTRIBUTE, COPY OR OTHERWISE USE IT.  IF YOU HAVE RECEIVED
THIS COMMUNICATION IN ERROR, PLEASE IMMEDIATELY NOTIFY THE SENDER BY
TELEPHONE OR EMAIL, AND DESTROY THIS MESSAGE AND ANY ATTACHMENTS.  THANK
YOU.”