On Thu, Mar 7, 2013 at 11:23 AM, Andrew Beekhof wrote:
> On Wed, Mar 6, 2013 at 8:02 PM, James Guthrie wrote:
>> Hi Andrew,
>>
>> Thanks for looking into this. We have since decided not to perform a
>> failover on the failure of one of the sub-* resources for operational
>> reasons. As a result
On Wed, Mar 6, 2013 at 8:02 PM, James Guthrie wrote:
> Hi Andrew,
>
> Thanks for looking into this. We have since decided not to perform a failover
> on the failure of one of the sub-* resources for operational reasons. As a
> result, I can't reliably test if this issue is actually fixed in the
On Wed, Mar 6, 2013 at 6:59 PM, James Guthrie wrote:
> On Mar 6, 2013, at 7:34 AM, Andrew Beekhof wrote:
>
>> 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 p
Hi Andrew,
Thanks for looking into this. We have since decided not to perform a failover
on the failure of one of the sub-* resources for operational reasons. As a
result, I can't reliably test if this issue is actually fixed in the current
HEAD. (Speaking of which, do you have a date set yet f
On Mar 6, 2013, at 7:34 AM, Andrew Beekhof wrote:
> 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 a
aker/pengine/pe-input-47.bz2):
Stopped\
>
> Regards,
> James
>
>
>
> On Feb 5, 2013, at 7:41 PM, David Vossel wrote:
>
>>
>>
>> - Original Message -
>>> From: "James Guthrie"
>>> To: "The Pacemaker cluster resource ma
s is a bug?
>
> Regards,
> James
>
>
>
> On Feb 5, 2013, at 7:41 PM, David Vossel wrote:
>
>>
>>
>> - Original Message -
>>> From: "James Guthrie"
>>> To: "The Pacemaker cluster resource manager"
>>>
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
Regards,
James
On Feb 6, 2013, at 8:14 PM, David Vossel wrote:
>
>
> - Original Message -
>> From: "James Guthrie"
>> To: "The Pacemaker cluster resource manager"
>> Sent: Wednesday, February 6, 2013 6:52:07 AM
>> Subject: Re: [Pa
- Original Message -
> From: "James Guthrie"
> To: "The Pacemaker cluster resource manager"
> Sent: Wednesday, February 6, 2013 6:52:07 AM
> Subject: Re: [Pacemaker] Pacemaker resource migration behaviour
>
> A quick addendum to this message:
gt;
>
> On Feb 5, 2013, at 7:41 PM, David Vossel wrote:
>
>>
>>
>> - Original Message -
>>> From: "James Guthrie"
>>> To: "The Pacemaker cluster resource manager"
>>> Sent: Tuesday, February 5, 2013 8:12:57 AM
>
- Original Message -
> From: "James Guthrie"
> To: "The Pacemaker cluster resource manager"
> Sent: Tuesday, February 5, 2013 8:12:57 AM
> Subject: Re: [Pacemaker] Pacemaker resource migration behaviour
>
> Hi all,
>
> as a follow-up t
Hi all,
as a follow-up to this, I realised that I needed to slightly change the way the
resource constraints are put together, but I'm still seeing the same behaviour.
Below are an excerpt from the logs on the host and the revised xml
configuration. In this case, I caused two failures on the ho
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.
Regards,
James
On Feb 5, 2013, at 10:56 AM, Andrew Beekhof wrote:
> On Thu, J
On Thu, Jan 31, 2013 at 3:04 AM, James Guthrie wrote:
> Hi all,
>
> I'm having a bit of difficulty with the way that my cluster is behaving on
> failure of a resource.
>
> The objective of my clustering setup is to provide a virtual IP, to which a
> number of other services are bound. The servic
Hi all,
I'm having a bit of difficulty with the way that my cluster is behaving on
failure of a resource.
The objective of my clustering setup is to provide a virtual IP, to which a
number of other services are bound. The services are bound to the VIP with
constraints to force the service to b
17 matches
Mail list logo
