check_dhcp issue

[Dei Bertine]

Ok some progress doing this command... :-)
chown root:root check_dhcp && chmod 4755 check_dhcp

However, what's odd is when I launch the plugin command via cli I am ok:
OK: Received 1 DHCPOFFER(s), max lease time = 86400 sec.

But when I look at the nagios monitor page, I get this:
CRITICAL: Received 1 DHCPOFFER(s), 0 of 1 requested servers responded, max lease time = 86400 sec. 


Any idea why? 



________________________________
From: Andreas Ericsson <ae at op5.se>
To: Dei Bertine <deibertine at yahoo.com>
Cc: nagios-users at lists.sourceforge.net
Sent: Thursday, June 25, 2009 10:58:14 PM
Subject: Re: [Nagios-users] check_dhcp issue

Dei Bertine wrote:
> Ok did that but still error:
> root at tool:/usr/local/nagios/libexec# chmod 4755 ./check_dhcp
> root at tool:/usr/local/nagios/libexec# ls -als check_dhcp
> 76 -rwsr-xr-x 1 nagios nagios 72834 2009-04-26 21:06 check_dhcp
> nagios at tool:~/libexec$ ./check_dhcp -s serveip1
> Error: Could not bind socket to interface eth0.  Check your privileges...
> 
> Any other ideas?
> 

Sorry. As root:
chown root:root check_dhcp && chmod 4755 check_dhcp

-- Andreas Ericsson                  andreas.ericsson at op5.se
OP5 AB                            www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090626/9afbb7fb/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
-------------- 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