dhcpd 3.0.1 stops responding to requests

[Glenn Satchell]

Hi Wil,

3.0.1 is pretty old, you should try upgrading to the latest release,
3.0.4 and see if the problem persists. There have been a *lot* of
bugfixes, especially to do with failover since 3.0.1 was released.

regards,
-glenn

>Subject: RE: dhcpd 3.0.1 stops responding to requests
>Date: Mon, 22 May 2006 17:11:24 -0700
>From: "Wil Birkmaier" <wil at bea.com>
>To: <dhcp-users at isc.org>
>
>Thanks Chuck, I will give that a try.
>
>On another note, I turned off ddns intermit setting as well as put it in
>stand alone mode.  It has been running for around 10 hours, so I shall
>see how that goes as well.
>
>Thanks!
>
>Wil
>
>-----Original Message-----
>From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On
>Behalf Of Chuck Anderson
>Sent: Monday, May 22, 2006 5:24 PM
>To: dhcp-users at isc.org
>Subject: Re: dhcpd 3.0.1 stops responding to requests
>
>On Mon, May 22, 2006 at 11:00:13AM -0700, Wil Birkmaier wrote:
>> Hello All, I have tried searching thru the archives as well as google
>> the last couple days and have come to my wits end trying to figure
>this
>> one out.  The only thought I have at this point is the failover has
>> problems with using other ports (Using 521 instead of 520) or WANs
>
>I don't think so.  I run multiple instances of failover on the same 
>dhcpd, each one using a different port starting at 520 and going up to 
>523.  I also set the peer port to the same port number.
>
>>         mclt 600;
>>         split 255;
>>         load balance max seconds 3;
>> }
>
>I think I read on here once that the split 255 may cause an issue.  
>I've always used the default split of 128.
>
>_______________________________________________________________________
>Notice:  This email message, together with any attachments, may contain
>information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
>entities,  that may be confidential,  proprietary,  copyrighted  and/or
>legally privileged, and is intended solely for the use of the individual
>or entity named in this message. If you are not the intended recipient,
>and have received this message in error, please immediately return this
>by email and then delete it.
>