dhcpd process hitting data size limit

David W. Hankins David_Hankins at isc.org
Tue Mar 25 22:13:16 UTC 2008

On Mon, Mar 03, 2008 at 03:26:12PM +0100, sthaug at nethelp.no wrote:
> Mar  3 14:23:26 dhcp2 dhcpd: failover: connect: no matching state.

are you sure the failover connection is entering 'normal' state on
both sides after a restart?  if it is, it is logged to syslog.

in 3.1.0, we adopted some stipulations in the ietf failover draft that
say the failover peers identify each other by the failover
relationship name, and not by ip address (as was done in 3.0.x).  so
if your failover {} config stanzas do not have a matching name, they
will not connect to each other.  well, they do connect, and then they
keep retrying when the connection is dropped.

when the failover stanzas don't have matching names, the above quoted
log message is emitted.

anyway, if your failover stanzas have different names, that would
explain what is different between your boxes and others (incl. our

Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
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