> 'make install-commandmode' does this. Sorry, yes, that is correct, and I did indeed do that. > Is your web server user a member of the nagios group in /etc/group? > Did you restart the web server after adding it to the group?
A-HA!!! Thanks, Marc!!!! That did it!! > Marc One other question, tho.... When I start up Nagios, I get two instances of the Nagios daemon: [10:27:19 root rockwell:/etc/init.d] ps -ef | grep nagios | grep -v nrpe nagios 23036 1 0 10:24 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg root 23205 2196 0 10:25 pts/1 00:00:00 tail -f /var/log/nagios/nagios.log nagios 23780 1 0 10:27 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 23781 23780 0 10:27 ? 00:00:00 /usr/local/nagios/libexec/check_ping -H 10.211.24.52 -w 3000.0,80% -c 5000.0,100% -p 5 nagios 23782 23781 0 10:27 ? 00:00:00 /bin/ping -n -U -w 30 -c 5 10.211.24.52 The lower-pid'd one is the one that is specified in the NagiosRunFile in the startup script: [10:27:16 root rockwell:/etc/init.d] cat /var/spool/nagios/run/nagios.lock 23036 However, all the children processes seem to be kicked off from the other 2nd daemon. When I run a "nagios stop", it kills the 2nd instance, leaving the first legitimate daemon running: [10:34:50 root rockwell:/etc/init.d] ./nagios stop Stopping nagios: kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] done. [10:36:38 root rockwell:/etc/init.d] ps -ef | grep nagios | grep -v nrpe nagios 23036 1 0 10:24 ? 00:00:01 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg And when I kill that one by hand, then I see in the nagios log that the process was killed: [10:38:24 root rockwell:/var/log/nagios] kill 23036 [10:39:59 root rockwell:/var/log/nagios] tail -4 nagios.log [1250876347] Warning: Return code of 127 for check of service 'GRID STATUS' on host 'Cal-ISO-Grid' was out of bounds. Make sure the plugin you're trying to run actually exists. [1250876367] SERVICE NOTIFICATION: kfreels;rockwell;MEMORY;CRITICAL;notify-service-by-email;Connection refused or timed out [1250876399] Caught SIGTERM, shutting down... [1250876399] Successfully shutdown... (PID=23036) Any thoughts? Thanks again!!! ....k -=-=-=- ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ 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
