Mr. Hopcroft, Thanks for your response on this issue. I turned on logging in the p1.pl and here's what I got. I have cut and pasted a couple of plugins as seen in the epn logfile and through the webui of nagios. I think epn is getting the correct response from the plugin, and the performance information looks good in the user interface, but the status field in the user interface has garbage data mixed in with valid data.
This is nagios-3.0a2 by the way. From epn_leave-msgs.log : Mon May 7 10:49:08 2007 run_package: "/usr/lib/nagios/plugins/check_rfinput -H10.0.5.26 -Cpublic -Onagios" returning (0, "-34 dBm|rf-input=34;58;60;22;80"). From Nagios Web UI: Current Status: OK (for 6d 4h 51m 46s) Status Information: �FdBm Performance Data: rf-input=34;58;60;22;80 Current Attempt: 1/1 (HARD state) Last Check Time: 05-07-2007 10:49:08 Check Type: ACTIVE Check Latency / Duration: 0.287 / 1.486 seconds From epn_leave-msgs.log : Mon May 7 10:58:03 2007 run_package: "/usr/lib/nagios/plugins/check_radio_status -H10.0.7.46 -Cpublic" returning (0, "Status: No Alarms Uptime: 297 Days UAS: 0 SES: 0"). From Nagios Web UI: Current Status: OK (for 24d 8h 39m 16s) Status Information: (No output returned from plugin) Performance Data: Current Attempt: 1/1 (HARD state) Last Check Time: 05-07-2007 10:58:03 Check Type: ACTIVE Check Latency / Duration: 156.153 / 3.484 seconds Please let me know if I need to try anything else. Thanks, James Whittington [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, May 03, 2007 10:23 PM To: [email protected] Subject: Re: [Nagios-users] Nagios 3.x + ePN = Garbage data in status ..[SEC=UNCLASSIFIED] Dear Sir, I am writing to thank you for your letter and say, > -----Original Message----- > Message: 11 > Date: Thu, 3 May 2007 12:04:09 -0700 > From: "Rob Brown" <[EMAIL PROTECTED]> > Subject: Re: [Nagios-users] Nagios 3.x + ePN = Garbage data in status > field? > > I am also seeing this same exact problem and am looking for a cure. No > luck so far. It would be helpful to determine if the problem is ePN returning a bogus return code or Nag 3.x not processing it correctly. You can do this by enabling ePN logging (see perldoc p1.pl). (You could also do the same with Nag logging but that requires Nagios compiled with the debug options). You will need to carefully edit p1.pl to set the DEBUG_LEVEL constant to LEAVE_MSG. Set the debug log path and name as suits you (or make sure the defaults aren't going to kill you). Restart Nagios. You should see messages like those documented. If they disagree with what Nagios is reporting then its a Nag bug, otherwise an ePN bug. Please let the list know your result. Yours sincerely. Classification: UNCLASSIFIED ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
