Evidently this is something that has since been fixed.
In your logs pe-input-47 results in:
<1d>Feb 6 09:37:52 mu pengine[6257]: notice: LogActions: Demote
conntrackd:1(Master -> Slave nu)\
<1d>Feb 6 09:37:52 mu pengine[6257]: notice: LogActions: Demote
condition:1 (Master -> Slave
On Wed, Feb 6, 2013 at 11:41 PM, James Guthrie wrote:
> Hi David,
>
> Unfortunately crm_report doesn't work correctly on my hosts as we have
> compiled from source with custom paths and apparently the crm_report and
> associated tools are not built to use the paths that can be customised with
>
Unfortunately the config only tells half of the story, the really
important parts are in the status.
Do you still happen to have
/opt/OSAGpcmk/pcmk/var/lib/pacemaker/pengine/pe-input-156.bz2 on mu
around? That would have what we need.
On Wed, Feb 6, 2013 at 1:12 AM, James Guthrie wrote:
> Hi all
On Tue, Feb 5, 2013 at 9:13 PM, James Guthrie wrote:
> Hi Andrew,
>
> "The resource" in this case was master-squid.init. The resource agent serves
> as a master/slave OCF wrapper to a non-LSB init script. I forced the failure
> by manually stopping that init script on the host.
Ok.
Generally i
Hi, Jiaju
There is a request about the log of booth.
I want you to change a log level when a ticket expires into "info" from "debug".
I think that this log is important since it means what occurred.
And I want you to add the following information to log.
* Which ticket is it?
* Who had a tick
Nodes shouldn't be being fenced so often. Do you know what is causing
this to happen?
You can also set resource-stickiness to prevent the resources
migrating back to A when it first comes back.
On Sun, Feb 24, 2013 at 9:11 PM, Jan Škoda wrote:
> Hello,
>
> I'm searching for a way to block stonit
On Thu, Feb 28, 2013 at 5:13 PM, Vladislav Bogdanov
wrote:
> 28.02.2013 07:21, Andrew Beekhof wrote:
>> On Tue, Feb 26, 2013 at 7:36 PM, Vladislav Bogdanov
>> wrote:
>>> 26.02.2013 11:10, Andrew Beekhof wrote:
On Mon, Feb 18, 2013 at 6:18 PM, Vladislav Bogdanov
wrote:
> Hi Andrew,
On Tue, Mar 5, 2013 at 4:20 AM, Leon Fauster wrote:
> Dear list,
>
> just to excuse the triviality - i started to deploy a ha environment
> in a test lab and therefore i do not have much experience.
>
>
>
> i started to setup a 2-node cluster
>
> corosync-1.4.1-15.el6.x86_64
> pacemaker-1.1.8-
On Wed, Mar 6, 2013 at 12:37 PM, wrote:
> Hi Dejan,
> Hi Andrew,
>
> As for the crm shell, the check of the meta attribute was revised with the
> next patch.
>
> * http://hg.savannah.gnu.org/hgweb/crmsh/rev/d1174f42f4b3
>
> This patch was backported in Pacemaker1.0.13.
>
> *
> https://github.
For ordering: yes, use resource sets with require-all=false
For colocation: no, its a much harder problem unfortunately
On Tue, Mar 5, 2013 at 6:51 AM, Doug Clow wrote:
> Hello,
>
> I have a Filesystem resource that is an NFS mount. This NFS resource is
> available at two separate IPs on two se
Hi Dejan,
Hi Andrew,
As for the crm shell, the check of the meta attribute was revised with the next
patch.
* http://hg.savannah.gnu.org/hgweb/crmsh/rev/d1174f42f4b3
This patch was backported in Pacemaker1.0.13.
*
https://github.com/ClusterLabs/pacemaker-1.0/commit/fa1a99ab36e0ed015f1bcbbb2
On Wed, Mar 6, 2013 at 2:01 AM, Michael Powell <
michael.pow...@harmonicinc.com> wrote:
> I have recently assumed the responsibility for maintaining code on one of
> my company’s products that uses Pacemaker/Heartbeat. I’m still coming up
> to speed on this code, and would like to solicit comment
> > 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")
Thank you for pointing that out, I found those changes to be very useful.
- Forwarded Message -
From: Jake Smith
To: Tommy Cooper ; The Pacemaker cluster resource
manager
Sent: Tuesday, March 5, 2013 4:13 PM
Subject: Re: [Pacemaker] Fw: Fw: Fw: Cluster resources failing to move
I jus
I just wanted to reiterate one thing that I think got lost at the bottom of my
first response - might be helpful...
You don't need these colocation and order statements if you have the resources
grouped. The group is a syntax shortcut for writing order and colocation
statements so the group is
I have recently assumed the responsibility for maintaining code on one of my
company's products that uses Pacemaker/Heartbeat. I'm still coming up to speed
on this code, and would like to solicit comments about some particular
behavior. For reference, the Pacemaker version is 1.0.9.1, and Hear
Thank you all for helping me, the problem appears to be solved
- Forwarded Message -
From: emmanuel segura
To: Tommy Cooper ; The Pacemaker cluster resource
manager
Sent: Tuesday, March 5, 2013 12:21 AM
Subject: Re: [Pacemaker] Fw: Fw: Cluster resources failing to move
try with thi
Hi,
I have a configuration problem with heartbeat usging crm on option. I only
use cluster IP as resource. I have 3 nodes and when 3 or 2 nodes are up it
works great, I can reach active node via cluster IP, but when only one node
is up, I cannot reach that node via cluster IP.
I am using
heartbe
18 matches
Mail list logo
