Failover woes with restarts of 4.0.0
David W. Hankins
David_Hankins at isc.org
Wed Jan 7 17:18:45 UTC 2009
On Wed, Jan 07, 2009 at 11:10:44AM +0000, Dean, Barry wrote:
> Jan 7 10:56:13 slave dhcpd: [ID 702911 daemon.info] DHCPREQUEST for aaa.bbb.66.156 from 00:14:38:8b:00:8f via e1000g2: lease 188.8.131.52 unavailable.
> Jan 7 10:56:13 slave dhcpd: [ID 702911 daemon.info] DHCPNAK on aaa.bbb.66.156 to 00:14:38:8b:00:8f via e1000g2
The unavailable log line probably means the lease is already assigned
to another client, or any situation that would cause the server to
think the client requesting that lease should not be allowed to have
If you've got one server OFFERing the lease, and the other server
NAKing the lease, then you should try to get back to synched servers
by faulting one of the lease databases. You may want to do this in
conjuction with a move to 4.0.2 (4.0.0 maint/bugfixes).
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil? https://secure.isc.org/store/t-shirt/
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 194 bytes
Desc: not available
More information about the dhcp-users