|
The nagevlog hang is a known bug with a (currently) unknown solution. Basically, what's going on is that it is unable to contact the NSCA daemon, so it tries to shut down. Before shutting down, it tries to notify the NSCA daemon that is going down. But it can't, so it decides to shut down... and so on, and so forth. This also causes GPFs when you shut down windows while NagEvLog is running, on occasion.
The solution is, of course, for the code to NOT try and notify NSCA of the problem when NSCA itself was the original fault. Due to the nature of the code, though, this is not so easy as you'd think (due to histroical reasons in the code).
You can kill the nagevlog.exe process to fix things, but this of course requires sysadmin privs. The hang on shutdown is not a real problem since everything is going down anyway (the TCPIP stack gets taken away before nagevlog gets to notifcy NSCA is appears).
I'll keep looking for a solution, once I get back to having development time (currently working on VMWare monitoring).
_________________ Steve Shipway UNIX Systems, ITSS, University of Auckland, NZ Woe unto them that rise up early in the morning... -- Isaiah 5:11
|