Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 427079

Summary:	Got too many timeouts in handshaking, ignoring client'
Product:	Red Hat Enterprise Linux 3	Reporter:	Wade Mealing <wmealing>
Component:	netdump	Assignee:	Neil Horman <nhorman>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	3.9	CC:	tao
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-12-31 23:20:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Wade Mealing 2007-12-31 00:22:06 UTC

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 23:20:59 UTC

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