check_logs permissions?

[Pavleck, Jeremy D.]

Run it as the user Nagios runs under, that will go a large way into figuring it out

--------------------------
Jeremy D. Pavleck via BlackBerry
Network Engineer - Systems Management
IT Network and Infrastructure Dept.
Capella Education Company
DIRECT: (612) 977 - 5881


-----Original Message-----
From: nagios-users-bounces at lists.sourceforge.net <nagios-users-bounces at lists.sourceforge.net>
To: nagios-users at lists.sourceforge.net <nagios-users at lists.sourceforge.net>
Sent: Tue Jun 27 22:17:35 2006
Subject: [Nagios-users] check_logs permissions?

Hello,

 

I’m trying having trouble getting check logs to work. As a test, I’ve been monitoring Apache’s error.log for any new lines (with the regular expression reg_exp => ‘.*’;

 

When I run check_logs.pl from the command line (logged in as root) it works fine, returning any new lines from the file. When run from Nagios, however, it returns either OK and a note that the plugin didn’t return anything, or if I chmod 666 error.log CRITICAL with the message ‘return code of 13 out of bounds.’ This leads me to believe it’s a problem with permissions, but I have no idea how I to fix them. Any help would be greatly appreciated.

 

Thanks in advance,

Martin.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060628/abd170e1/attachment.html>
-------------- next part --------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
-------------- next part --------------
_______________________________________________
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