> -----Original Message-----
> From: Lacayo, Luis F [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 27, 2007 3:07 PM
> To: Marc Powell; [email protected]
> Subject: RE: [Nagios-users] check_dhcp question...
> 
> Here is the output of the verbose.
> 
> [EMAIL PROTECTED] libexec]#  ./check_dhcp -v -s 10.129.177.16
> Requested server address: 10.129.177.16
> DHCP socket: 3
> Hardware address: 001438bbfc21
> DHCPDISCOVER to 255.255.255.255 port 67
> DHCPDISCOVER XID: 756149105 (0x2D11EB71)
> DHCDISCOVER ciaddr:  0.0.0.0
> DHCDISCOVER yiaddr:  0.0.0.0
> DHCDISCOVER siaddr:  0.0.0.0
> DHCDISCOVER giaddr:  0.0.0.0
> send_dhcp_packet result: 548
> 
> No (more) data received
> Result=ERROR
> Total responses seen on the wire: 0
> Valid responses for this machine: 0
> DHCP problem: No DHCPOFFERs were received.

I assume that this machine is on the same broadcast network as your DHCP
server and they are truly different machines. Are you running dhclient
or iptables/ipchains on this machine? Anything that would interfere with
the reception of the dhcp packet? It might be necessary to use tcpdump
to verify that the machine is actually receiving a response. Right now
it would appear that it really isn't.

How were the plugins installed and what version? If you're not running
the latest version of the plugins you should test with that. This thread
might be useful --

http://sourceforge.net/tracker/index.php?func=detail&aid=1090549&group_i
d=29880&atid=397597

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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

Reply via email to