Bug 427079 - Got too many timeouts in handshaking, ignoring client'
Got too many timeouts in handshaking, ignoring client'
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: netdump (Show other bugs)
3.9
All Linux
low Severity low
: ---
: ---
Assigned To: Neil Horman
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-30 19:22 EST by Wade Mealing
Modified: 2007-12-31 18:20 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-12-31 18:20:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Wade Mealing 2007-12-30 19:22:06 EST
Description of problem:

Attempting to talk to a netdump server on a non critical port, creates the error
messages "Got too many timeouts in handshaking, ignoring client".


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

netdump-0.6.11-3-i386
netdump-server-0.6.11-3-i386

How reproducible:


Steps to Reproduce:
1. Setup netdump to dumb on non standard port
2. Test basic netdump logging
3. Panic machine
  
Actual results:

Logs hit disk, core never hits disk

Expected results:

Core to hit disk.

Additional info:

Workaround to use a standard port, but this is not available/a solution in this
customers situation.

Customer has been informed that this does not meet inclusion criteria for
RHEL3U9 as this is clearly in maintenance mode.
Comment 2 Neil Horman 2007-12-31 18:20:59 EST
Yeah, sorry, this is a wontfix, although theres not enough data here to really
analyze the problem.  Best suggestion would be to go get the netdump-server
package from EPEL for RHEL5 and retest with that.  If that fails in the same
way, open a bug on that, or reopen this one against that component, and we can
track down the problem.

FWIW, I vaguely recall a bug that we fixed in RHEL4 for netdump regarding
non-standard port usage for netdump, but I think it required that the crashing
machine was also acting as a netdump server

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