Non obvious 127 plugin error

[Craig Stewart]

Justin,

I ran across that one as well and set the following in nagios.cfg:

enable_environment_macros=0

This didn't help.  I do have a fairly large config (about 8k hosts and
12k service checks) but I didn't think it was THAT big.

Actually the check_dig command isn't the only one that isn't working.
The "service-notify-by-email" command also barfs on the output of SOME
checks, not all.  This is simply a "printf blah blah blah" command
defined in Nagios, not a compiled plug in. The check_ping command works,
but I understand it's just a wrapper for the ping command itself.  A
number of custom bash and perl check commands work, but admittedly I
simply pass the $HOSTNAME$ to them as an argument.

I've rewritten the DNS-Check command so that everything except the
$HOSTNAME$ is "hard coded" but I don't think this will work.  I'm
admittedly grasping at straws now.  This is what the command line will
look like:

/usr/lib/nagios/plugins/check_dns -s $HOSTADDRESS$ -H www.xplornet.com
-a 142.166.86.46 -w 0.25 -c 5 -t 10

Craig

Craig Stewart
Systems Integration Analyst
Craig.Stewart at corp.xplornet.com
Xplornet - Broadband, Everywhere

On 06/02/2011 02:07 PM, Justin T Pryzby wrote:
> Ah, I think it may be due to a ngaios setting of
> "enable_environment_macros":
> nagios.sourceforge.net/docs/3_0/configmain.html
> 
> Nagios [can] export all sorts of data relating to the state of the
> check, and that can be useful, but it seems as if your configuration
> is too big or complicated or such to fit.  Do your other checks work?
> What if you make their argument list as long as for check_dig?
> I think it's possible that some checks are run with bigger inherited
> environment than other checks, due to servicegroups and such.  The
> execve() E2BIG error is due to a kernel limit on the size of "argument
> list plus environment".  You could also write a check (or replace the
> check_dig command) with something like "set
>>/var/lib/nagios3/nagios-environment" or some other nagios-writable
> path.  There shouldn't be more than (say) a kilobyte of environment.
> It's also possible that you're sourceing something huge like
> /etc/bash_completion, but that doesn't explain why it doesn't affect
> your user accounts and other nagios checks.  Or you can rerun the
> strace with "-v" to cause the environment to be displayed.
> 
> Justin
> 

------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
_______________________________________________
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