> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of qeldroma > Sent: Monday, December 05, 2005 8:45 AM > To: nagios-users@lists.sourceforge.net > Subject: Re: [Nagios-users] Probs with nagios-service/status > > > What is your nagios_check_command in cgi.cfg? When you ran your test, > > did you use the exact command line as specified there? > nagios_check_command=/usr/bin/perl /usr/nagios/libexec/check_nagios_db.pl > and YES, it works from console as root and "su nagios".. > > > Also, when you see the error in the CGI, there is a link to follow for > more > > information. What does that page say is the reason it thinks nagios > > isn't running? > ------------------------------------------------------------------------ -- > -------------------- > Process Status: > UNKNOWN > Check Command Output: Nagios check command did not return any output > ------------------------------------------------------------------------ -- > -------------------- > > But that's the point: It worked as nagios (the user of the process)..?!
My mistake for not remembering this initially... nagios isn't the user running the check_nagios_db.pl process but rather the user that your web server is running as. I would verify that your web server process has permissions to run that script in that directory (normal apache(?) directives and/or SELinux if it's enabled) and is actually able to run it. -- Marc ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ 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