Yes, but that also made it worse :( There's only one process running, but Nagios now reports three. I am really stuck here.
>From /etc/nagios/nrpe.cfg on admin1 command[check_pdns_recursor]=/etc/nagios/pdns_recursor.sh root@admin1:/etc/nagios# less pdns_recursor.sh #!/bin/bash /usr/lib/nagios/plugins/check_procs -w 1:1 -c 1:1 -a pdns_recursor root@monitor1:~# /bin/bash -c "/usr/lib/nagios/plugins/check_nrpe -H admin1.cgx1.prod.conviva.com -c check_pdns_recursor" PROCS CRITICAL: 3 processes with args 'pdns_recursor' root@admin1:/etc/nagios# ps wgaux | grep recursor root 14508 0.0 0.0 8952 876 pts/1 S+ 18:59 0:00 grep --color=auto recursor pdns 25186 0.0 0.0 110124 1884 ? Ssl Aug09 0:03 /usr/sbin/pdns_recursor --config-dir=/etc/powerdns/recursor-public.d C O N V I V A Kimberly McKinnis | Systems Engineer, Service Delivery | [email protected] | Mobile: 724.612.2716 | 2 WATERS PARK DRIVE | SUITE 150 | SAN MATEO | CA | 94403 | www.conviva.com | On 8/10/11 11:43 AM, "[email protected]" <[email protected]> wrote: > >I have no idea, but that would seem unlikely. Have you tried my other >suggestion?: > >command[check_pdns_config_pub]=/path/to/your/bash-script > >in bash-script: > >#!/bin/bash > >/usr/lib/nagios/plugins/check_procs -w 1:1 -c 1:1 -a pdns_recursor > > >In effect creating a bash wrapper for the plugin. > >> Thank you for that observation. I was being dumb with the quoting. >> ButSit's still not working correctly. >> >> The commands work properly on the command line on the host (admin1), but >> the Nagios server (monitor1) sees +1 count again. I am very confused by >> this. Does Nagios server force it back to the dash shell in Ubuntu? I >> thought maybe the +1 was transient because I ran the check manual, but >>all >> of the checks are also reporting +1 and I haven't run them manually. >> >> My check looks like: command[check_pdns_recursor]=/bin/bash -c >> "/usr/lib/nagios/plugins/check_procs -w 1:1 -c 1:1 -a pdns_recursor" >> >> >> root@admin1:~# /bin/bash -c "/usr/lib/nagios/plugins/check_procs -w 1:1 >>-c >> 1:1 -a pdns_recursor" >> PROCS OK: 1 process with args 'pdns_recursor' >> >> But the server reports: >> >> >> root@monitor1:/etc/nagios3/conf.d# /usr/lib/nagios/plugins/check_nrpe -H >> admin2.cgx1.prod.conviva.com -c check_pdns_recursor >> PROCS CRITICAL: 2 processes with args 'pdns_recursor' >> >> >> >> >> >> C O N V I V A >> Kimberly McKinnis | Systems Engineer, Service Delivery | >>[email protected] | >> Mobile: 724.612.2716 | >> 2 WATERS PARK DRIVE | SUITE 150 | SAN MATEO | CA | 94403 | >> www.conviva.com | >> >> >> >> >> >> On 8/9/11 5:17 PM, "[email protected]" <[email protected]> wrote: >> >>>> 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" >>> >>>Wait...looks like your quotes are in the wrong place. Try: >>> >>> 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" >>> >>>Everything after -c should be in double quotes. >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>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 >>>[email protected] >>>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 >> >> >> >>------------------------------------------------------------------------- >>----- >> 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 >> [email protected] >> 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 >> > > >-------------------------------------------------------------------------- >---- >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 >[email protected] >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 ------------------------------------------------------------------------------ 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 [email protected] 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
