[Nagiosplug-devel] [ nagiosplug-Bugs-1648570 ] check_dhcp error by asking 2 dhcp servers

[SourceForge.net]

Bugs item #1648570, was opened at 2007-01-31 09:36
Message generated for change (Comment added) made by fhackenbmt
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1648570&group_id=29880

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: fhackenbmt (fhackenbmt)
Assigned to: Nobody/Anonymous (nobody)
Summary: check_dhcp error by asking 2 dhcp servers

Initial Comment:
nagios-plugins 1.4.5 contains the check_dhcp version 1.6, wich has problems with some dhcp-server setups
check_dhcp version 1.7 from nagios-plugins version 1.4 works without problems, so please include the this version or fix included version.

so what is the porblem with the check_dhcp 1.6?
we have 2 dhpc-servers and if I ask one of them, the check_dhcp plugins
says:
=======snip=======
monitor:~# /usr/lib/nagios/plugins/check_dhcp -v -s 192.168.0.221
Requested server address: 192.168.0.221
DHCP socket: 3
Hardware address: 00163e0f931c
DHCPDISCOVER to 255.255.255.255 port 67
DHCPDISCOVER XID: 427952544 (0x198209A0)
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

recv_result_1: 333
recv_result_2: 333
receive_dhcp_packet() result: 333
receive_dhcp_packet() source: 192.168.0.222
Result=OK
DHCPOFFER from IP address 192.168.0.237 via 192.168.0.222
DHCPOFFER XID: 427952544 (0x198209A0)
DHCPOFFER chaddr: 00163E0F931C
DHCPOFFER ciaddr: 0.0.0.0
DHCPOFFER yiaddr: 192.168.0.97
DHCPOFFER siaddr: 192.168.0.237
DHCPOFFER giaddr: 0.0.0.0
Option: 53 (0x01)
Option: 54 (0x04)
Option: 51 (0x04)
Option: 1 (0x04)
Option: 3 (0x04)
Option: 6 (0x0C)
Option: 58 (0x04)
Option: 59 (0x04)
Lease Time: 3600 seconds
Renewal Time: 1800 seconds
Rebinding Time: 3150 seconds
Added offer from server @ 192.168.0.237 of IP address 192.168.0.97


recv_result_1: 333
recv_result_2: 333
receive_dhcp_packet() result: 333
receive_dhcp_packet() source: 192.168.0.221
Result=OK
DHCPOFFER from IP address 192.168.0.237 via 192.168.0.221
DHCPOFFER XID: 427952544 (0x198209A0)
DHCPOFFER chaddr: 00163E0F931C
DHCPOFFER ciaddr: 0.0.0.0
DHCPOFFER yiaddr: 192.168.0.72
DHCPOFFER siaddr: 192.168.0.237
DHCPOFFER giaddr: 0.0.0.0
Option: 53 (0x01)
Option: 54 (0x04)
Option: 51 (0x04)
Option: 1 (0x04)
Option: 3 (0x04)
Option: 6 (0x0C)
Option: 58 (0x04)
Option: 59 (0x04)
Lease Time: 3600 seconds
Renewal Time: 1800 seconds
Rebinding Time: 3150 seconds
Added offer from server @ 192.168.0.237 of IP address 192.168.0.72


No (more) data received
Result=ERROR
Total responses seen on the wire: 2
Valid responses for this machine: 2
CRITICAL: Received 2 DHCPOFFER(s), 0 of 1 requested servers responded,
max lease time = 3600 sec.
=======snap=======
as yo can see the requested servers (192.168.0.221) have answerd.



----------------------------------------------------------------------

>Comment By: fhackenbmt (fhackenbmt)
Date: 2007-05-29 12:07

Message:
Logged In: YES 
user_id=1706299
Originator: YES

this problem is reproducible with the current release.
it do not occur on check_dhcp from nagios-plugins version 1.4 

fyio: I have to dhcp servers,
one is master, the other ist slave.
the config is similar to:
http://www.lithodyne.net/docs/dhcp/dhcp-4.html

----------------------------------------------------------------------

Comment By: Subhendu Ghosh (sghosh)
Date: 2007-05-28 20:05

Message:
Logged In: YES 
user_id=46572
Originator: NO

It looks like 192.168.0.221 is a relay.  You actual dhcp server thinks (or
is configured) as 192.168.0.237.


----------------------------------------------------------------------

Comment By: Matthias Eble (psychotrahe)
Date: 2007-05-28 11:55

Message:
Logged In: YES 
user_id=1694341
Originator: NO

hi fhackenbmt,

I cannot understand the versioning problem. check_dhcp 1.7 is not tagged
and should hence not have been part of any release.

Is this problem still reproducible with the current release?

Thanks for your Report
Matthias

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1648570&group_id=29880