Location-constraints for fencing-resources are definitely supported and
don't just work by accident - if this was the question.
On 09/13/2016 02:43 AM, Dan Swartzendruber wrote:
> On 2016-09-12 10:48, Dan Swartzendruber wrote:
>> Posting this as a separate thread from my fence_apc one. As I said
On 2016-09-12 10:48, Dan Swartzendruber wrote:
Posting this as a separate thread from my fence_apc one. As I said in
that thread, I created two fence_apc agents, one to fence node A and
one to fence node B. Each was configured using a static pcmk node
mapping, and constrained to only run on the
Posting this as a separate thread from my fence_apc one. As I said in
that thread, I created two fence_apc agents, one to fence node A and one
to fence node B. Each was configured using a static pcmk node mapping,
and constrained to only run on the other node. In the process of
testing thi
On 09/12/2016 03:00 PM, Alex wrote:
> Hi Klaus,
>
> Thanks for the reply.
>
> I dont have any logs to indicate that was indeed the PID of apache but
> I believe apache was killed successfully as I logged on the server
> apache wasn't running.
Reason for me asking was rather if it might have been
Hi Klaus,
Thanks for the reply.
I dont have any logs to indicate that was indeed the PID of apache but I
believe apache was killed successfully as I logged on the server apache wasn't
running.
I am running:corosync-2.3.2-2
pacemaker-1.1.10-19
Thanks,Alex
On Monday, September 12, 2016 1:03
On 09/12/2016 12:55 PM, Alex wrote:
> Hi all,
>
> I am having a problem with one of our pacemaker clusters that is
> running in an active-active configuration.
>
> Sometimes the Website monitor will timeout, triggering and apache
> restart that fails. That will increase the fail-count to INFINITY f
