As an aside, it is starting on the primary, but will fail to start on
the secondary during a fail-over, so I suspect there is some work I now
need to do in the script itself.
Florian has made a request of me that I'm going to try to full-fill
today, and that might make it easier to do.
On Fri, 2
Hi Andreas,
I've made the changes you've suggested, and while the grouping is
working nicely, I'm still getting a "not installed" error for DHCP
itself. However, on closer inspection it still looks like it is
attempting to start DHCP on the secondary node. Here is the updated
configuration based
Hello Chris,
On 12/01/2011 06:25 PM, Chris Bowlby wrote:
> Hi Everyone,
>
> I'm in the process of configuring a 2 node + DRBD enabled DHCP cluster
> using the following packages:
>
> SLES 11 SP1, with Pacemaker 1.1.6, corosync 1.4.2, and drbd 8.3.12.
>
> I know about DHCP's internal fail-over
On Thu, 2011-12-01 at 13:25 -0400, Chris Bowlby wrote:
> Hi Everyone,
>
> I'm in the process of configuring a 2 node + DRBD enabled DHCP cluster
This doesn't really address your specific question, but I got dhcpd to
work by using the ocf:heartbeat:anything RA.
primitive dhcp ocf:heartbeat:anyth
Hi Everyone,
I'm in the process of configuring a 2 node + DRBD enabled DHCP cluster
using the following packages:
SLES 11 SP1, with Pacemaker 1.1.6, corosync 1.4.2, and drbd 8.3.12.
I know about DHCP's internal fail-over abilities, but after testing, it
simply failed to remain viable as a more
