"peer holds all free leases" message

[Nick Garfield]

Next time you have a problem with "peer holds all free leases" take a
look at these values, then checkout top to see the IOWAIT values.  The
box with a high load thrashes the disk IO and makes the IOWAIT go
through the roof while also stuffing all network based IO.  I never
found the root cause of these events - but that is what makes your
communications-interrupted messages.  I presume you are running linux
simply because I have never seen this problem reported on solaris.....

What lease times (max,min,default) and value of mclt are configured?
The post shows ~5000 active leases - how many subnets is this
distributed over?

> -----Original Message-----
> From: dhcp-users-bounce at isc.org 
> [mailto:dhcp-users-bounce at isc.org] On Behalf Of Kirsten Petersen
> Sent: Tuesday, October 03, 2006 12:00 AM
> To: dhcp-users at isc.org
> Subject: RE: "peer holds all free leases" message
> 
> ns1:
> load average: 0.29, 0.25, 0.19
> 
> ns2:
> load average: 0.09, 0.17, 0.17
> 
> 
> And that's typical for these boxes.  They only run dhcp and bind.
> 
> ________________
> Kirsten Petersen
> Network Services * Oregon State University
> http://oregonstate.edu/net * irc.oregonstate.edu #osu-is
> "If you're not learning, you're not living."
> 
> On Mon, 2 Oct 2006, Nick Garfield wrote:
> 
> > What's the load on each box? (copy paste the output of uptime)
> >
> >> -----Original Message-----
> >> From: dhcp-users-bounce at isc.org
> >> [mailto:dhcp-users-bounce at isc.org] On Behalf Of Kirsten Petersen
> >> Sent: Monday, October 02, 2006 10:40 PM
> >> To: dhcp-users at isc.org
> >> Subject: Re: "peer holds all free leases" message
> >>
> >> I don't see any BNDUPD messages, but I am seeing a lot of these:
> >>
> >> Oct  2 00:10:02 ns1 dhcpd: failover peer dhcp: I move from 
> normal to
> >> communications-interrupted
> >> Oct  2 00:10:06 ns2 dhcpd: failover peer dhcp: I move from 
> normal to
> >> startup
> >> Oct  2 00:10:06 ns1 dhcpd: failover peer dhcp: I move from
> >> communications-interrupted to startup
> >> Oct  2 00:10:06 ns1 dhcpd: failover peer dhcp: I move from 
> startup to
> >> communications-interrupted
> >> Oct  2 00:10:06 ns2 dhcpd: failover peer dhcp: peer moves
> >> from normal to
> >> communications-interrupted
> >> Oct  2 00:10:06 ns2 dhcpd: failover peer dhcp: I move from 
> startup to
> >> normal
> >> Oct  2 00:10:06 ns1 dhcpd: failover peer dhcp: peer moves
> >> from normal to
> >> normal
> >> Oct  2 00:10:06 ns1 dhcpd: failover peer dhcp: I move from
> >> communications-interrupted to normal
> >> Oct  2 00:10:06 ns2 dhcpd: failover peer dhcp: peer moves from
> >> communications-interrupted to normal
> >> Oct  2 06:40:06 ns2 dhcpd: failover peer dhcp: I move from 
> normal to
> >> startup
> >> Oct  2 06:40:06 ns1 dhcpd: failover peer dhcp: I move from
> >> communications-interrupted to startup
> >> Oct  2 06:40:06 ns1 dhcpd: failover peer dhcp: I move from 
> startup to
> >> communications-interrupted
> >> Oct  2 06:40:06 ns2 dhcpd: failover peer dhcp: peer moves
> >> from normal to
> >> communications-interrupted
> >> Oct  2 06:40:06 ns2 dhcpd: failover peer dhcp: I move from 
> startup to
> >> normal
> >> Oct  2 06:40:06 ns1 dhcpd: failover peer dhcp: peer moves
> >> from normal to
> >> normal
> >> Oct  2 06:40:06 ns1 dhcpd: failover peer dhcp: I move from
> >> communications-interrupted to normal
> >> Oct  2 06:40:06 ns2 dhcpd: failover peer dhcp: peer moves from
> >> communications-interrupted to normal
> >> Oct  2 08:00:02 ns1 dhcpd: failover peer dhcp: I move from 
> normal to
> >> communications-interrupted
> >> Oct  2 08:00:06 ns2 dhcpd: failover peer dhcp: I move from 
> normal to
> >> startup
> >> Oct  2 08:00:06 ns1 dhcpd: failover peer dhcp: I move from
> >> communications-interrupted to startup
> >> Oct  2 08:00:06 ns1 dhcpd: failover peer dhcp: I move from 
> startup to
> >> communications-interrupted
> >> Oct  2 08:00:06 ns2 dhcpd: failover peer dhcp: peer moves
> >> from normal to
> >> communications-interrupted
> >> Oct  2 08:00:06 ns2 dhcpd: failover peer dhcp: I move from 
> startup to
> >> normal
> >> Oct  2 08:00:06 ns1 dhcpd: failover peer dhcp: peer moves
> >> from normal to
> >> normal
> >> Oct  2 08:00:06 ns1 dhcpd: failover peer dhcp: I move from
> >> communications-interrupted to normal
> >> Oct  2 08:00:06 ns2 dhcpd: failover peer dhcp: peer moves from
> >> communications-interrupted to normal
> >>
> >>
> >> The times are synchronized on the two servers.
> >>
> >> ________________
> >> Kirsten Petersen
> >> Network Services * Oregon State University
> >> http://oregonstate.edu/net * irc.oregonstate.edu #osu-is
> >> "If you're not learning, you're not living."
> >>
> >> On Mon, 2 Oct 2006, David W. Hankins wrote:
> >>
> >>> On Sun, Oct 01, 2006 at 09:55:05AM -0700, Kirsten Petersen wrote:
> >>>> primary:
> >>>> active: 2572
> >>>> backup: 5835
> >>>> free: 4543
> >>>> expired: 2591
> >>>> released: 3
> >>>>
> >>>> secondary:
> >>>> active: 2577
> >>>> backup: 5834
> >>>> free: 4517
> >>>> expired: 2586
> >>>> released: 4
> >>>
> >>> Huh.  I'm not sure what's going on here.  Are you getting any
> >>> BNDUPD failures logged to syslog?  Any failover sylogs at all?
> >>>
> >>> --
> >>> ISC Training!  October 16-20, 2006, in the San Francisco Bay Area,
> >>> covering topics from DNS to DDNS & DHCP.  Email training at isc.org.
> >>> --
> >>> 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
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
> 
>