Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SSuppSocket:Fatal error

Status
Not open for further replies.

thepallace

Technical User
Jun 8, 2004
48
US
We are getting this error and whta caused this error to generate. Pls advise.


grpsvcs_2_19.aixprod.bak:Sep 30 08:30:27 TRACE_FYI : in SSuppSocket::HandleInput(void): Fatal error(or socket disconnection) reading supplicant message header on fd[321]. SockError=0 Len=-3
grpsvcs_2_19.aixprod.bak:Sep 30 08:40:27 TRACE_FYI : in SSuppSocket::ReadData(void *p, int readlen: fatal errorerrno=17
grpsvcs_2_19.aixprod.bak:Sep 30 08:40:27 TRACE_FYI : in SSuppSocket::HandleInput(void): Fatal error(or socket disconnection) reading supplicant message header on fd[321]. SockError=0 Len=-3
grpsvcs_2_19.aixprod.bak:Sep 30 08:45:57 TRACE_FYI : in SSuppSocket::ReadData(void *p, int readlen: fatal errorerrno=17
grpsvcs_2_19.aixprod.bak:Sep 30 08:45:57 TRACE_FYI : in SSuppSocket::HandleInput(void): Fatal error(or socket disconnection) reading supplicant message header on fd[130]. SockError=0 Len=-3
grpsvcs_2_19.aixprod.bak:Sep 30 08:50:26 TRACE_FYI : in SSuppSocket::ReadData(void *p, int readlen: fatal errorerrno=17
grpsvcs_2_19.aixprod.bak:Sep 30 08:50:26 TRACE_FYI : in SSuppSocket::HandleInput(void): Fatal error(or socket disconnection) reading supplicant message header on fd[321]. SockError=0 Len=-3
grpsvcs_2_19.aixprod.bak:Sep 30 09:00:27 TRACE_FYI : in SSuppSocket::ReadData(void *p, int readlen: fatal errorerrno=17
grpsvcs_2_19.aixprod.bak:Sep 30 09:00:27 TRACE_FYI : in SSuppSocket::HandleInput(void): Fatal error(or socket disconnection) reading supplicant message header on fd[321]. SockError=0 Len=-3
grpsvcs_2_19.aixprod.bak:Sep 30 09:00:51 TRACE_FYI : in SSuppSocket::ReadData(void *p, int readlen: fatal errorerrno=17
grpsvcs_2_19.aixprod.bak:Sep 30 09:00:51 TRACE_FYI : in SSuppSocket::HandleInput(void): Fatal error(or socket disconnection) reading supplicant message header on fd[321]. SockError=0 Len=-3
grpsvcs_2_19.aixprod.bak:Sep 30 09:00:56 TRACE_FYI : in SSuppSocket::ReadData(void *p, int readlen: fatal errorerrno=17
grpsvcs_2_19.aixprod.bak:Sep 30 09:00:56 TRACE_FYI : in SSuppSocket::HandleInput(void): Fatal error(or socket disconnection) reading supplicant message header on fd[321]. SockError=0 Len=-3

Thanks,
JAQ

 
hi ,
sounds like you need an OS fix , have a look at the following taken from
if something similar , then worth checking with IBM if a fix is out for this problem

APAR: IY26148 COMPID: 5765D5101 REL: 121
ABSTRACT: HAEMD INTERNAL ERROR CAUSES CLSTRMGR TO HALT


PROBLEM DESCRIPTION:
When a provider is failed during the 'failure' protocol and
the default vote value is "REJECT," an error can occur in hags
which then disrupts clstrmgr.
An errpt entry will show:
LABEL: HA002_ER
IDENTIFIER: 12081DC6
...
Detail Data
DETECTING MODULE
LPP=PSSP,Fn=emd_gsi.c,SID=1.4.1.30,L#=933,
DIAGNOSTIC EXPLANATION
haemd: 2521-007 Internal error (2).
Shortly after haemd will core dump, and at that time the
grpsvc log will show:
TRACE_FYI : in SSuppSocket::HandleInput(void): Fatal error(or
socket disconnection) reading supplicant message header on
fd[9]. SockError=0 Len=-2
TRACE_FYI : in SVProtocol::Rejected(void): Group name
[ha_em_peers] Protocol [FailureLeave] has been rejected!
[{provider}Member token[-1] [pgsProvider]
ProviderId[65535/65535/(0/5/5)]]
TRACE_FYI : in SFailureProtocol::RejectedPostBroadcast(void):
Implicit rejection of a failure protocol!
Not long after clstrmgr will come down (core dump as well).


PROBLEM SUMMARY:
haemd is core dumping when during the processing of the
failure protocol, a providor fails. The errpt shows
an HA002_ER entry with the following message:
haemd: 2521-007 Internal error (2).


PROBLEM CONCLUSION:
haemd has been modified, so that during processing of the
failure protocol, if a providor fails, the new failure
protocol will be ignored.


------
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top