Dear Stanley,
Thank you for your reply. I double checked configure options, and I am
pretty certain that I don't have ePN compiled into Nagios. Yet every
Perl plugin returns No Output...
As suggested I moved this topic to devel as it is about 2.0a1.
Kind regards,
Tom
Stanley Hopcroft wrote:
>Dear Sir,
>
>I am writing to thank you for your letter and say,
>
>On Fri, Aug 13, 2004 at 08:30:39PM -0700, [email protected] wrote:
>
>
>
>>From: "Tom DE BLENDE (GCC)"
>>To: nagios-users
>>Subject: [Nagios-users] Perl problems in Nagios 2.0a1
>>
>>Hi folks,
>>
>>Am I being a complete dork, or is there a bug in Nagios 2.0a1 that makes
>>it unable to use any of my Perl plugins? They work just fine in 1.0 (on
>>another box) and from the CLI (when being su - 'd to Nagios user).
>>
>>
>>
>
>There seem to be at least two issues here
>
>1 changes to configure to use ePN by default - if that's what you got
>(/bin/nagios -m will tell you).
>
>In any case, configure --help will show the options to disable ebedded
>Perl interpreter
>
>2 changes to ePN
>
>2.1 to deal with leaks by periodically reload interp (should set
>upper bound on nag mem usage) ==> unlikely to be source of probs
>
>2.2 changes to p1.pl and interface to nag in checks.c (me) ==> prob
>culprit.
>
>I haven't looked at 2.0 for a while but these latter changes have been
>solid with 1.2 for yonks.
>
>Have a look at the p1.pl text and see if you feel like enabling 'war and
>peace mode' debugging (think it's called 'debug' or sim) by editing
>p1.pl and posting me the log.
>
>perldoc /bin/p1.p1 should tell you what to do. OTOH the
>docco is __slack__.
>
>Since this is a bug in a devel branch may be better on nagios-devel
>
>
>
>>I'm puzzled. I just get the "(No Output!)" thing...
>>
>>Thanks,
>>Tom
>>
>>
>>
>>
>
>Yours sincerely.
>
>
>
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]