General questions about failover, config changes and restarting
james.dore at new.ox.ac.uk
Fri Mar 4 11:00:01 UTC 2016
> On 3 Mar 2016, at 16:45, S Carr <sjcarr at gmail.com> wrote:
> On 3 March 2016 at 15:02, James Dore <james.dore at new.ox.ac.uk> wrote:
>> Any ideas why my servers need so many restarts? I try to leave them to settle for five or six minutes before trying again, but they just seem to stick with things like
>> dhcpd.log-20151123:2015-11-23T10:17:58.203346+00:00 garibaldi dhcpd: failover peer newc-dhcp: I move from normal to shutdown
>> dhcpd.log-20151123:2015-11-23T10:18:03.848105+00:00 garibaldi dhcpd: failover peer newc-dhcp: I move from shutdown to startup
>> dhcpd.log-20151123:2015-11-23T10:18:03.854208+00:00 garibaldi dhcpd: failover peer newc-dhcp: peer moves from normal to communications-interrupted
>> dhcpd.log-20151123:2015-11-23T10:18:03.927644+00:00 garibaldi dhcpd: failover peer newc-dhcp: I move from startup to shutdown
>> dhcpd.log-20151123:2015-11-23T10:18:03.940208+00:00 garibaldi dhcpd: failover peer newc-dhcp: peer moves from communications-interrupted to partner-down
> So what version of DHCPD are you running, a (stupid) feature was
> introduced in a particular version (now regressed) to automatically
> enter partner-down on a shut down, that is the root of your problems,
> you should not be entering partner-down at all as the partner is not
> down, and then it has to go through it's recovery stage to get back
> into normal mode. Also check the init script to make sure it's not
> doing anything silly with omshell to initiate a shutdown as that will
> also trigger partner-down.
> Others on the list might be able to comment which version this change
> was regressed in.
It’s version 4.2.6 as shipped with SLES12.
More information about the dhcp-users