"peer holds all free leases" message
Kirsten Petersen
kirsten.petersen at oregonstate.edu
Mon Mar 13 22:55:50 UTC 2006
Another piece of information wrt this problem: in the course of
troubleshooting this, my colleague noticed that the time was way off
between the two servers - by an hour, actually.
Could this time mismatch issue be responsible for the servers getting out
of sync with each other? After we fixed the time and I put the old leases
file back in place, all of the errors ("peer holds all free leases", and
"not responding (recovering)") went away, and things are working okay
again.
________________
Kirsten Petersen
Network Services * Oregon State University
http://oregonstate.edu/net * irc.oregonstate.edu #osu-is
"Go to the edge of the cliff and jump off. Build your wings on the way down."
- Ray Bradbury
On Mon, 13 Mar 2006, Kirsten Petersen wrote:
> This problem has just bit us in the rear again.
>
> A couple of our subnets started getting the "peer holds all free leases"
> error again, on both servers. I tried the work-around that worked last
> time - stopping dhcp on the secondary and nuking the leases file - but it
> didn't change anything this time. The errors persisted.
>
> In an act of desperation, I whacked the leases file on the primary, too.
> Now it is in recover and is saying "not responding (recovering)" to many
> requests, although it is ACKing some requests, too. Strangely, the
> dhcpd.leases file does not contain any leases yet...
>
> So, apparently that wasn't such a good idea. Is there anything I can do
> to prevent this "peer holds all free leases" issue from coming up again?
> I'm feeling very powerless right now. :( Perhaps our config should be
> different. This is the present config:
>
> Primary:
>
> failover peer "dhcp" {
> primary;
> address 128.193.x,x;
> port 520;
>
> # our peer is ns2
> peer address 128.193.x.2x;
> peer port 520;
>
> max-response-delay 60;
> max-unacked-updates 10;
> mclt 3600;
> split 128;
> load balance max seconds 3;
> }
>
> secondary:
>
> failover peer "dhcp" {
> secondary;
> address 128.193.x,x;
> port 520;
>
> # ns1 is our secondary
> peer address 128.193.x.x;
> peer port 520;
>
> max-response-delay 60;
> max-unacked-updates 10;
> mclt 3600;
> load balance max seconds 3;
> }
>
> We are running 3.03. Any suggestions are welcome. Would it be better to
> set these up so that the secondary is just an emergency failover? Also,
> where can I find detailed information about how the failover and pool
> sharing works? (It's all voodoo to me at this point.)
>
> Thanks.
>
> ________________
> Kirsten Petersen
> Network Services * Oregon State University
> http://oregonstate.edu/net * irc.oregonstate.edu #osu-is
> "Go to the edge of the cliff and jump off. Build your wings on the way down."
> - Ray Bradbury
>
> On Wed, 1 Mar 2006, David W. Hankins wrote:
>
>> *** From dhcp-server -- To unsubscribe, see the end of this message. ***
>>
>> On Tue, Feb 28, 2006 at 04:43:07PM -0800, Kirsten Petersen wrote:
>>> What's the ETA on a release candidate for 3.0.4?
>>
>> I'm not aware of anything that would cause me to schedule another beta.
>>
>> So, hopefully in 1-2 weeks, so long as nothing crops up.
>>
>> b2->b3 took forever because I found a crash bug here on our systems at
>> ISC...releasing b3 knowing it would crash means we know we'll have a
>> b4, so it's just a waste of time. Ultimately, we didn't actually fix
>> that bug (was never able to find it), we just backed out the change that
>> seems to have produced it, scheduling it for rework into a later release.
>>
>> --
>> 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
>>
>> -----------------------------------------------------------------------
>> List Archives : http://www.isc.org/ops/lists/
>> Unsubscribe : http://www.isc.org/sw/dhcp/dhcp-lists.php
>> -or- : mailto:dhcp-server-request at isc.org?Subject=unsubscribe
>> -----------------------------------------------------------------------
>>
>>
>
>
More information about the dhcp-users
mailing list