"peer holds all free leases" message

Kirsten Petersen kirsten.petersen at oregonstate.edu
Tue Oct 3 05:37:58 UTC 2006


Duh.  I feel silly now.

We push frequent changes to the dhcp servers, and reboot them whenever 
something changes, which can be as often as every 5 minutes.  Is this a 
Bad Idea?  Could this be what causes the servers to get out of sync?  If 
so, I guess we'll have to rethink our design...

________________
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, Kirsten Petersen wrote:

> 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
>>
>>
>>
>
>
>


More information about the dhcp-users mailing list