> Il 09/05/2011 19:53, Jochen Bern ha scritto:
>>
>> Do you use environment variables in the first place? (I.e., a plugin,
>> event handler, notification command etc. which reads a $NAGIOSsomething
>> variable from its environment, rather than having it passed on the
>> command line through a $something$ macro in the Nagios config.) If not,
>
> AFAIK we don't use environment variables (and grepping for NAGIOS in the
> config file led me only to commented out strings).
>
>> try setting "enable_environment_macros=0" in your nagios.cfg (it's
>> usually a performance boost, anyway).
>
> Yep, this did the trick. After setting "enable_environment_macros=0" the
> missing plugin notification did disappear.
> Also if this workarounds the problem I'll be glad to do further
> testing/analysis to catch it down (this is a pre-prod system so testing
> is easy).
>
Ah. I'll see about getting a patch in to catch superlong environment
macros. In general, environment macros is a very, very bad idea for large
environments, precisely for this reason.
> Kind regards
> R
>
> PS: I'll be @Nagios World Conference in Bolzano next Tuesday so if
> someone wants to give a closer look...
>
Neat. I'll be there too. Not that this problem needs further investigation
now though, but still
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]