Bug 111061 - netdump does not start without NETDUMPADDR
netdump does not start without NETDUMPADDR
Status: CLOSED DUPLICATE of bug 109943
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: netdump (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Anderson
Depends On:
  Show dependency treegraph
Reported: 2003-11-26 16:16 EST by jacob liberman
Modified: 2007-11-30 17:06 EST (History)
0 users

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

Attachments (Terms of Use)

  None (edit)
Description jacob liberman 2003-11-26 16:16:28 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
Per netdump documentation, netdump should be able to start with only 
a SYSLOGADDR, and a NETDUMPADDR should not be required to log kernel 
oops to remote syslog server.

However, after spcifying remote SYSLOGADDR in /etc/sysconfig/netdump, 
netdump fails to start with error "Server address not specified 
in /etc/sysconfig/netdump" and netconsole driver cannot be manually 
loaded from command line. 

I believe the problem could be fixed if the /etc/rc.d/init.d/netdump 
did not fail after check for the NETDUMPADDR variable in all cases.

Please see bug 97663 for additional details.

Thanks, Jacob

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

How reproducible:

Steps to Reproduce:
1.echo "SYSLOGADDR=" >> /etc/sysconfig/netdump
2.start syslogd on with -r -x
3.service netdump start

Additional info:
Comment 1 Dave Anderson 2003-12-01 09:23:40 EST

*** This bug has been marked as a duplicate of 109943 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:00:12 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.