not responding (recover wait)

Thomas Zenz Thomas.Zenz at oenb.at
Thu Jun 8 07:21:00 UTC 2006


Hi all,

Today at 0:15 our master DHCP Server died. Failover recognized
partner-down. But then it changed to potential-conflict and stopped
answering to DHCP requests with the log entry not responding (recover
wait).
Even when the master was up and running again (8 hours later) the state
did not change. So I manualy changed the state to partner state to
down.

We have Version 3.0.3r3, on a gentoo system. Gentoo dose not recommend
the version 3.0.4r1 where may Failover issues are fixed. Is there a
reason?

tx
regards
Thomas Zenz


Leases entries from the secondary:

failover peer "BackUP" state {
  my state partner-down at 5 2006/05/26 05:48:34;
  partner state partner-down at 5 2006/05/26 05:48:34;
  mclt 1209600;
}

failover peer "BackUP" state {
  my state partner-down at 5 2006/05/26 05:48:34;
  partner state partner-down at 5 2006/05/26 05:48:34;
  mclt 1209600;
}

failover peer "BackUP" state {
  my state partner-down at 5 2006/05/26 05:48:34;
  partner state partner-down at 5 2006/05/26 05:48:34;
  mclt 1209600;
}

failover peer "BackUP" state {
  my state partner-down at 5 2006/05/26 05:48:34;
  partner state potential-conflict at 5 2006/05/26 05:48:34;
  mclt 1209600;
}

failover peer "BackUP" state {
  my state potential-conflict at 4 2006/06/08 05:50:20;
  partner state potential-conflict at 5 2006/05/26 05:48:34;
  mclt 1209600;
}

failover peer "BackUP" state {
  my state potential-conflict at 4 2006/06/08 05:50:20;
  partner state normal at 5 2006/05/26 05:48:34;
  mclt 1209600;
}


failover peer "BackUP" state {
  my state normal at 4 2006/06/08 05:50:24;
  partner state normal at 5 2006/05/26 05:48:34;
  mclt 1209600;
}



More information about the dhcp-users mailing list