problem about check_dhcp {Disarmed} {Fraud?}

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Per Jørgensen
> Sent: Friday, July 28, 2006 9:59 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] problem about check_dhcp {Disarmed} {Fraud?}
> 
> Hi Users!
> 
> I am running into a problem about check_dhcp plugin.
> My user nagios have not the rigth privileges to run this(Even thoug it
> have the exact same rigths as all the others plugins)
> When I run the plugin from a commandline as root - no problem!
> When I run as nagios user:
> /usr/local/nagios/libexec/check_dhcp -s 10.80.10.150
> Error: Could not bind socket to interface eth0.  Check your privileges...
> 

[snip]
> The rigths in libexec:
> -rwxr-xr-x  1 root   root    61374 Jul 28 13:16 check_dhcp

[snip]

> And there it is - no problem by running all the other plugins - but on
> this one I havent got the rigths.
> 
> Its running on a SUSE system as a Distributed server..
> What should I do to make nagios get the rigths to make this  dhcp check???

su -; chown root /usr/local/nagios/libexec/check_dhcp; chmod u+s /usr/local/nagios/libexec/check_dhcp

check_dhcp must be run as the root user. Making it owned by root and suid will allow nagios to run it as the root user with no special actions necessary. This would/should have been the default permissions after plugin installation.

--
Marc

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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