[Spread-users] Sess_validate_read_header: Message has illegal type field 0x80000080

Jonathan Stanton jonathan at cnds.jhu.edu
Wed Apr 20 14:38:36 EDT 2005


Hi,

I have not seen this particular bug before, but several bugs were 
fixed in 3.17.3 which could cause some corruption in the client-server 
messages and I would definitely suggest trying to reproduce the 
bug in 3.17.3 as it might already be fixed. The changelog on the website 
can be read here:

http://www.spread.org/changelog.html

and documents these fixes.

If it is still present in 3.17.3 then I'll probably generate a custom 
debugging patch for you to apply as the normal alarms will not help with 
this type of problem. 

Cheers,

Jonathan


On Tue, Apr 19, 2005 at 11:15:47PM -0400, Scott Barvick wrote:
> Yep, we have been running very well on 3.17.2 for quite a while.  
This may have just started due to increased load, and it is now easily
reproducible.  Is there anywhere I should focus or try upgrading?
>  
> Thanks,
> Scott
> 
> ________________________________
> 
> From: Ryan Caudy [mailto:rcaudy at gmail.com]
> Sent: Tue 4/19/2005 8:18 PM
> To: Scott Barvick
> Cc: spread-users at lists.spread.org
> Subject: Re: [Spread-users] Sess_validate_read_header: Message has illegal type field 0x80000080
> 
> 
> 
> The interaction there seems fairly normal -- if I had to guess, I
> would say that this points to a memory-corrupting bug.  I assume this
> is version 3.17.2 or 3.17.3?
> 
> Cheers,
> Ryan
> 
> On 4/19/05, Scott Barvick <sbarvick at revasystems.com> wrote:
> > Greetings,
> >
> > I'm getting the following error when running with a few test systems,
> > and I'm curious if others have seen anything similar.  I believe we are
> > hitting it medium hard with sends between 2 systems.  When I disconnect
> > one system with a hard stop of the app, the other system sees this,
> > processes the membership changes, but then a short time later kills the
> > client session when it receives a type field that has no type bits set
> > (only the endian bit - 0x80000080).
> >
> > I turned on SESSION and GROUP debug logging and included the output
> > below.  I was looking through the code to see how a message can get
> > through without the (FIFO_MESS | SELF_DISCARD) bits set as we send them
> > with the SP_multicast() call.  It probably is significant that the group
> > just dropped from 2 members to 1 member (the sender), but this works
> > fine in the steady state operation, even with only one member.
> >
> > Any similar experience or thoughts?
> >
> > Thanks,
> > Scott
> >
> > -------------------
> >
> > [...] lots more where this came from
> >
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > *****  Other system goes down ******
> > Send_join: State is 4
> > Send_join: State is 4
> > Memb_handle_token: handling form2 token
> > Handle_form2 in FORM
> > Memb_transitional
> > G_handle_trans_memb:
> > G_handle_trans_memb in GOP
> > G_handle_trans_memb: Received trans memb id of: {proc_id: -1408236782
> > time: 1113940766}
> > Memb_regular
> > Membership id is ( -1408236782, 1113940767)
> > --------------------
> > Configuration at testsys8 is:
> > Num Segments 1
> >         1       239.16.3.18       4803
> >                 testsys8                   172.16.3.18
> > ====================
> > G_handle_reg_memb:  with (172.16.3.18, 1113940767) id
> > G_handle_reg_memb in GTRANS
> > G_handle_reg_memb: skipping state transfer for group RTestGroup.
> > G_handle_reg_memb: skipping state transfer for group TTestGroup.
> > G_handle_reg_memb: skipping state transfer for group GTestGroup.
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > ******** start to receive membership messages ******
> > received TRANSITIONAL membership for group RTestGroup
> > Received REGULAR membership for group RTestGroup with 1 members, where I
> > am member 0:
> >         #RTEST0#testsys8
> > grp id is -1408236782 1113940767 1
> > Due to NETWORK change. VS set has 1 members:
> >         #RTEST0#testsys8
> > received TRANSITIONAL membership for group TTestGroup
> > received TRANSITIONAL membership for group GTestGroup
> > Received REGULAR membership for group TTestGroup with 1 members, where I
> > am member 0:
> >         #TTEST0#testsys8
> > grp id is -1408236782 1113940767 1
> > Due to NETWORK change. VS set has 1 members:
> >         #TTEST0#testsys8
> > Received REGULAR membership for group GTestGroup with 1 members, where I
> > am member 0:
> >         #TTEST0#testsys8
> > grp id is -1408236782 1113940767 1
> > Due to NETWORK change. VS set has 1 members:
> >         #TTEST0#testsys8
> > ***** we thought things were ok *******
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> >
> > ******  Something isn't right ************
> > Sess_read: Message has type field 0x80000080
> > Sess_validate_read_header: Message has illegal type field 0x80000080
> > SP_error: (-8) Connection closed by spread
> > Sess_kill: killing session RTEST0 ( mailbox 14 )
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> > Sess_read: Message has type field 0x800000c4
> > Sess_read: queueing message of type 4 with len 0 to the protocol
> >
> > _______________________________________________
> > Spread-users mailing list
> > Spread-users at lists.spread.org
> > http://lists.spread.org/mailman/listinfo/spread-users
> >
> 
> 

> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users


-- 
-------------------------------------------------------
Jonathan R. Stanton         jonathan at cs.jhu.edu
Dept. of Computer Science   
Johns Hopkins University    
-------------------------------------------------------




More information about the Spread-users mailing list