> > Attached is an excerpt from our two node (active/passive) Web cluster. We
> > are currently launching uWSGI via the ocf:heartbeat:anything RA (see below).
> >
> > I would like to make some slight changes to the "cmdline_options" argument
> > on our running cluster... (via "crm configure edit")
Attached is an excerpt from our two node (active/passive) Web cluster. We are
currently launching uWSGI via the ocf:heartbeat:anything RA (see below).
I would like to make some slight changes to the "cmdline_options" argument on
our running cluster... (via "crm configure edit")
Do I need to sto
cemaker@oss.clusterlabs.org
>Subject: Re: [Pacemaker] DRBD Split-brain (recovered), but still
> showing "Failed Actions"
>Message-ID: <4f84b03a.4030...@hastexo.com>
>Content-Type: text/plain; charset="iso-8859-1"
>
>On 04/10/2012 05:43 PM, Reid
11:23:41 +0200
>From: Andreas Kurz
>To: pacemaker@oss.clusterlabs.org
>Subject: Re: [Pacemaker] DRBD Split-brain (recovered), but still
> showing "Failed Actions"
>Message-ID: <4f83fc1d.9010...@hastexo.com>
>Content-Type: text/plain; charset="iso-8859-1&
We recently had a DRBD (v8.3.12) split brain scenario on our two-node
Active/Passive web cluster. The failover worked as expected, and we were
manually able to resolve the split brain scenario without issue.
However, CRM MON is still showing the following "Failed Actions" which I would
like to
Anton,
FWIW, I ran into the same issue not being able to ping IPs created this
wayŠwhen I checked "iptables -L" I realized that there were firewall rules
created that needed to be accounted for.
What worked for me was to try two things: 1.) If you can, temporarily
disable your firewall to ensure
You would think so :) I waited 2-3x the monitor interval in hopes the
Failed resources would eventually be setup, but that was not the case. To
Dejan's point, I could have checked the logs to look for something more
specific, but I did not. I've not heard of ocf_tester, perhaps it could
shed some l
D" IP starts I
was receiving. No worries, however, I am very happy with IPaddr2 as a VIP
solution, I was just hoping I could take advantage of the simplified
configuration (much easier on the eyes) ;)
Best,
- Mike
>Hi,
>
>On Mon, Jan 23, 2012 at 08:05:34PM +, Reid, Mike wrote:
>&
FYI,
The solution turned out to be related to IPTABLES rules that were added
using this approach.
By adding a custom IPTables "CLUSTERIP" chain, the firewall started
letting everything through :)
Unfortunately, it seems that this approach is somewhat experimental and
not very stable, so while I
Dejan,
Yes, thank you. I realized I was missing "unique_clone_address" in the
config, which made _most_ of the difference.
However, now I'm seeing some weirdness with regards to ARP -- In my setup,
I currently have three elastic IPs configured (effectively a small sample
of my intended IP Range),
Greetings! I am wondering if anyone here might be familiar with managing IP
ranges in Pacemaker? (e.g. via ocf:heartbeat:IPaddr2 and clone /
globally-unique="true"...I am using Pacemaker v1.0.9)
The reason I ask is because I'm only seeing the first IP address get created
and am wondering if per
Ivan,
Can you post your configuration? Do you have STONITH enabled?
I ran into similar issues in our Active/Active OCFS2/DRBD until we had a
functioning STONITH, fwiw.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.or
I've been doing a lot of testing while I've been learning Pacemaker/Heartbeat,
DRBD, OCFS2, etc (Nginx, PHP-FPM, Apache…) Below I've attached my working CIB,
but I worry I am missing something obvious (or perhaps going about it
incorrectly altogether): It seems I cannot start the cluster as a s
Lars,
Thank you for your comments. I did confirm I was running 8.3.8.1, and I have
even upgraded to 8.3.10 but am still experiencing the same I/O lock issue. I
definitely agree with you, DRBD is behaving exactly as instructed, being
properly fenced, etc.
I am quite new to DRBD (and OCFS2), lea
14 matches
Mail list logo
