"xid mismatch" problem is repeated infinitely

[Denis Laventure]

I have the same message here, I run 3.1. More than one/minutes.

Sep 18 12:52:42 dnsa dhcpd: bind update on 172.19.0.66 got ack from
failover-uqac: xid mismatch.
Sep 18 12:53:07 dnsa dhcpd: bind update on 172.19.0.136 got ack from
failover-uqac: xid mismatch.
Sep 18 12:53:11 dnsa dhcpd: bind update on 172.19.0.225 got ack from
failover-uqac: xid mismatch.
Sep 18 12:54:14 dnsa dhcpd: bind update on 172.19.0.31 got ack from
failover-uqac: xid mismatch.
Sep 18 12:54:22 dnsa dhcpd: bind update on 172.19.0.56 got ack from
failover-uqac: xid mismatch.
Sep 18 12:54:25 dnsa dhcpd: bind update on 172.19.0.81 got ack from
failover-uqac: xid mismatch.

David W. Hankins a écrit :
> On Tue, Sep 18, 2007 at 12:18:43PM +0400, Abu Abdulla alhanbali wrote:
>> Sep 18 08:19:29 iwandhcp-01 dhcpd: [ID 702911 local2.info] DHCPACK on
>> 172.17.169.57 to 00:10:6d:15:cb:30 via 172.17.168.2 Sep 18 08:19:29
> 
> If _this line_ is being repeated, then you need to go and find the
> device that is issuing the DHCPREQUEST prior and silence it, or
> configure dhcpd to ignore this client (by mac address or etc).
> 
> These are responses to client behaviour.
> 
>> iwandhcp-01 dhcpd: [ID 702911 local2.info] bind update on 172.17.169.57 got
>> ack from dhcp-failover: xid mismatch.
> 
> It's kind of strange, but this is a 3.1 bug that got fixed, actually.
> 
> Seeing these log messages is kind of a stopgap until we can get a
> bit more architecture around the problem of multiple queued updates.
> 

-- 
Denis Laventure
Technicien en informatique
Service des Technologies de l'Information
Université du Québec à Chicoutimi