On Apr 18, 2013, at 12:06 PM, Jose Pedro Oliveira <jpo(a)di.uminho.pt> wrote:
On 2013-04-18 19:11, Tim Wojtulewicz wrote:
> I recently installed the nagios, nagios-common, nagios-plugins, and a
> few of the nagios-plugins-* packages for EL6 from EPEL. I've run into a
> problem where nagios can't find the plugins at all. It gives me an
> error 127 when trying to find them, which from the nagios documentation
> means it thinks the plugins aren't installed. After a bit of debugging,
> it appears nagios is looking for the plugins to be installed in
> /usr/lib/nagios/plugins whereas the nagios packages in EPEL install them
> all in /usr/lib64/nagios/plugins. Creating a symlink from
> /usr/lib64/nagios to /usr/lib/nagios resolves that issue, but it doesn't
> seem to me that I should have to do that.
> Once I resolved the "not found" problem, nagios moved onto a permissions
> issue. Calling any plugin results in a 126 error code. I've tried
> 'chown -R nagios:nagios /usr/lib64/nagios'. This results in a lot of
> complaints that plugins need to be owned by root or should be setuid
> root. The permissions on the plugins and all of the directories above
> seem like the nagios user should be able to run the scripts (i.e.
> everything has o+rx at least).
> Any ideas? Thanks.
Please post the output of the following command:
rpm -q nagios nagios-common nagios-plugins
Apologies for the noise. This ended up being an issue with my build of check_mk using a
hard-coded directory for the nagios plugins, point at /usr/lib/nagios. I'll work with
that group as to whether their setup scripts can handle reading user variables out of the