Red Hat Bugzilla – Bug 185592
netdump LOCALPORT option not passed for 2.6 kernels
Last modified: 2007-11-30 17:07:24 EST
Description of problem:
The netdump LOCALPORT value is not being passed to the netdump module for 2.6
kernels. This creates a problem for systems that are configured as both a
netdump server and client as they both default to port 6666 (the default
localport of 6667 seems like a better approach to allow a netdump server to
point to a back-up server in order to save it's own panic information)
Version-Release number of selected component (if applicable):
How reproducible: Easy
Simply configure both netdump and netdump-server on a system. External clients
trying to dump to this system will fail to handshake because the client code has
beaten the server to the 6666 port. Setting the LOCALPORT variable in
/etc/sysconfig/netdump will have no effect as the netdump module is not being
passed the value.
The following diff illustrates the change needed to the /etc/init.d/netdump script:
# diff -au netdump.orig netdump
--- netdump.orig 2006-03-15 09:05:30.000000000 -0800
+++ netdump 2006-03-15 09:05:55.000000000 -0800
@@ -254,7 +254,7 @@
$TGTMAC $MHZ $IDLETIMEOUT"
# The netdump subsystem of the netconsole module is not configured.
I would also like to see the script changed so that the default for LOCALPORT is
something other than 6666 to avoid confusion for the customers that try to set
up both the client and server.
Thanks, I've checked this in. I'll file an errata when U5 opens.
The component of this request is planned to be updated in Red Hat enterprise
This enhancement request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux maintenance release.
Product Management has requested further review of this enhancement by Red Hat
Engineering, for potential inclusion in a Red Hat Enterprise Linux Update
release for currently deployed products.
This enhancement is not yet committed for inclusion in an Update release.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.