<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>Lease "not on its queue" Error</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Hey Everyone,<BR>
<BR>
We're just working on a failover deployment using 3.1.1 with 2 servers. It seems that now whenever we add a new pool definition, the failover causes the primary server to exit out, with the following messages:<BR>
<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd: Sending updates to failover-peer.<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd: Lease with binding state free not on its queue.<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd:<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd: If you did not get this software from ftp.isc.org, please<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd: get the latest from ftp.isc.org and install that before<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd: requesting help.<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd:<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd: If you did get this software from ftp.isc.org and have not<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd: yet read the README, please read it before requesting help.<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd: If you intend to request help from the dhcp-server@isc.org<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd: mailing list, please read the section on the README about<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd: submitting bug reports and requests for help.<BR>
Jun 28 20:47:54 dhcp-sac-1s dhcpd:<BR>
Jun 28 20:47:55 dhcp-sac-1s dhcpd: Please do not under any circumstances send requests for<BR>
Jun 28 20:47:55 dhcp-sac-1s dhcpd: help directly to the authors of this software - please<BR>
Jun 28 20:47:55 dhcp-sac-1s dhcpd: send them to the appropriate mailing list as described in<BR>
Jun 28 20:47:55 dhcp-sac-1s dhcpd: the README file.<BR>
Jun 28 20:47:55 dhcp-sac-1s dhcpd:<BR>
Jun 28 20:47:55 dhcp-sac-1s dhcpd: exiting.<BR>
<BR>
The error occurs after restarting the primary and it does a pool rebalance. I current add the new pool to the secondary, restart it, then add it to the primary and restart it.<BR>
<BR>
The fix is to remove the lease file on the SECONDARY and restart both which seems to allow it come back up. Any thoughts?<BR>
<BR>
The failover config is:<BR>
<BR>
failover peer "failover-peer" {<BR>
primary;<BR>
address x.x.x.x;<BR>
port 520;<BR>
peer address x.x.x.x;<BR>
peer port 520;<BR>
max-response-delay 60;<BR>
max-unacked-updates 10;<BR>
mclt 3600;<BR>
split 128;<BR>
load balance max seconds 3;<BR>
}<BR>
<BR>
<BR>
failover peer "failover-peer" {<BR>
secondary;<BR>
address x.x.x.x;<BR>
port 520;<BR>
peer address x.x.x.x;<BR>
peer port 520;<BR>
max-response-delay 60;<BR>
max-unacked-updates 10;<BR>
load balance max seconds 3;<BR>
}<BR>
<BR>
We also saw some times where it would say "backup" instead of "free" in the error message.<BR>
<BR>
Nicola<BR>
</FONT>
</P>
</BODY>
</HTML>