From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131 Description of problem: Scenario: Usage of net-console without sending crashdumps SYSLOGADDR is set to the appropriate address. NETDUMPADDR remains unset. Version-Release number of selected component (if applicable): netdump-0.6.6-1 How reproducible: Always Steps to Reproduce: 1. service netdump start 2. 3. Actual Results: NETDUMPADDR not set Expected Results: Netdump should work without crashdumps, crash signature is suffcient in most cases Additional info: FIX: /etc/init.d/netdump - [ -z "$NETDUMPADDR" ] && { + [ -z "$NETDUMPADDR -o -z $SYSLOGADDR" ] && { echo "Server address not specified in /etc/sysconfig/netdump" 1>&2 exit 1 }
*** Bug 111061 has been marked as a duplicate of this bug. ***
*** Bug 111261 has been marked as a duplicate of this bug. ***
Created attachment 96267 [details] proposed netdump init script
In addition to the netdump/syslog configuration issue the error-handling in the current netdump init script is almost non-existant; after a failire is detected, it just continues instead of stopping. The proposed version that's attached above handles all of the "service netdump start" error conditions.
The fix has been applied to: netdump-0.6.11-2 for AS2.1 netdump-0.6.11-3 for RHEL3 The netdump errata for both AS2.1-U3 and RHEL3-U1 have been updated to include this fix. However, since the beta versions of these errata have already been released, the changes will not be seen until those errata have been updated.
An errata 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. http://rhn.redhat.com/errata/RHEA-2003-355.html