Bug 126750 - ccsd doesn't handle close from cman_tool leave properly
ccsd doesn't handle close from cman_tool leave properly
Status: CLOSED DUPLICATE of bug 126958
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: gfs (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jonathan Earl Brassow
Derek Anderson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-06-25 14:44 EDT by Derek Anderson
Modified: 2010-01-11 21:53 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 14:04:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Derek Anderson 2004-06-25 14:44:55 EDT
Description of problem:

After quorum was achieved in a three node cluster I started removing
nodes with 'cman_tool leave'.  Then noticed around 2 million of these
message per minute in the /var/log/messages file:

Jun 25 19:17:34 link-10 ccsd[5329]: Received bad communication type on
cluster socket.

Added some debug to cluster/ccs/daemon/cman_mgr.c:
Index: cman_mgr.c
===================================================================
RCS file: /cvs/cluster/cluster/ccs/daemon/cman_mgr.c,v
retrieving revision 1.1
diff -r1.1 cman_mgr.c
116a117
>       log_err("recvmsg returned %d\n", len);
118,119c119,121
<       log_dbg("Msg looks like:\n");
<       log_dbg("%s\n", (char *)&ch);
---
>       log_err("Msg looks like:\n");
>       log_err("Type is %d\n", ch.comm_type);
>       log_err("%s\n", (char *)&ch);

Error output then looks like:
Jun 25 19:17:34 link-10 ccsd[5329]: recvmsg returned 0
Jun 25 19:17:34 link-10 ccsd[5329]: Received bad communication type on
cluster socket.
Jun 25 19:17:34 link-10 ccsd[5329]: Msg looks like:
Jun 25 19:17:34 link-10 ccsd[5329]: Type is 0

So it seems ccsd is not handling a client close properly.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jonathan Earl Brassow 2004-06-29 17:26:22 EDT

*** This bug has been marked as a duplicate of 126958 ***
Comment 2 Kiersten (Kerri) Anderson 2004-11-16 14:13:04 EST
Updating version to the right level in the defects.  Sorry for the storm.
Comment 3 Red Hat Bugzilla 2006-02-21 14:04:13 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.