Nagios 3.x + ePN = Garbage data in status .. [SEC=UNCLASSIFIED]

[Stanley.Hopcroft at Dest.gov.au]

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" <dtownrobbrown at gmail.com>
> 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
Nagios-users at lists.sourceforge.net
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