check_dhcp permissions issue even when run as root

Maxwell Carey <[email protected]>
Newsgroups gmane.network.nagios.user
Message-ID <[email protected]>
I'm having a strange issue with the check_dhcp plugin v1.4.16 on SL6. 
Permissions on the file are 4750, owner is root, and group is nagios; 
the nagios user is a member of the nagios group. The partition was 
mounted with the suid option enabled. SELinux is disabled.

$ ls -l /usr/local/nagios/libexec/check_dhcp
-rwsr-x--- 1 root nagios 123851 Jun  3 12:08 
/usr/local/nagios/libexec/check_dhcp

When I run check_dhcp as the nagios user, I get the following error:

$ /usr/local/nagios/libexec/check_dhcp
Error: Could not bind socket to interface eth0.  Check your privileges...

Even when I run the plugin as the root user, I get the same error, so I 
suspect this is not really a file permissions issue.

I found a similar post on this list from 2008 
(http://sourceforge.net/mailarchive/message.php?msg_id=20407079), but 
when that poster changed the permissions to 0775 he was able to run the 
plugin successfully as root. But when I chmod 0775 and run as root I 
still get the same error. The last post in the thread simply says "was a 
permission issue on the file" with no additional explanation, which is 
oh so helpful. Does anyone have any idea what could cause this?

--Max Carey

------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Nagios-users mailing list
[email protected]
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.