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): netdump-0.6.10-2 How reproducible: Always Steps to Reproduce: 1.echo "SYSLOGADDR=172.16.10.1" >> /etc/sysconfig/netdump 2.start syslogd on 172.16.10.1 with -r -x 3.service netdump start Additional info:
*** This bug has been marked as a duplicate of 109943 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.