Description of problem: The netdump server daemon ("netdump-server" service) does not execute the "netdump-start" script in "/var/crash/scripts" directory when netdump service is activated on a RHEL4 GA/U1/U2/U3 netdump client. This is due to a RHEL4 GA/U1/U2/U3 kernel bug in which a netdump client does not send the prerequisite "[...network console startup...]" message in the init_netconsole() function of driver/net/netconsole.c. Instead, it would send the message "netconsole: network logging started\n", which is not recognized by the netdump-server. Although this is being addressed in the RHEL4-U4 kernel (BZ #177628), to maintain backwards-compatibility for systems still running the older kernels, the netdump-server should be updated to recognize both messages as indicative of a client starting up. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I fixed this in the "upstream" version of netdump (0.7.15-1). To avoid repeating the nightmare of putting in fixes-without-bugzillas during the next netdump errata, I'm doing this after-the-fact.
*** This bug has been marked as a duplicate of 177628 ***