> After wondering why all of the processes I'm checking with check_procs > were counting an extra, I discovered the bug with /bin/dash under Debian > [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626913] > > As a workaround (because I'm not interested in changing the default shell > for the entire server), I called /bin/bash when defining my commands in > nrpe.cfg. Now they're going haywire in a different way. For instance: > > command[check_pdns_config_pub]=/bin/bash -c > /usr/lib/nagios/plugins/check_procs -w 1:1 -c 1:1 -a "pdns_server > --config-name=public" > > But now Nagios reports: "PROCS OK: 271 processes" > > I am baffled. Every process I am checking now reports 271, which is how > many total processes are running. Prior to explicitly defining the shell > in the command, it was reporting correctly but adding one process to the > count, so I shouldn't have broken it too badly here. > > Any suggestions on a better workaround? Thanks!
I am just guessing here, but it looks apparent that the arguments after check_procs aren't being passed along to the shell. Just for gags, have you tried taking the "-c" out, if necessary, by invoking the plugin from a separatge bash shell script (without -c) with all the arguments in the script? ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Nagios-users mailing list Nagios-users@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
