On 2011-04-15 08:23, Andrew Beekhof wrote:
> On Fri, Apr 15, 2011 at 7:51 AM, Florian Haas wrote:
>> Andrew,
>>
>> the documentation states that unless your distro ships
>> dlm_controld.pcmk, you should be installing cman and running Pacemaker
>> on that. I presume this is because (at least on Fed
On Thu, Apr 14, 2011 at 6:39 PM, Carlos G Mendioroz wrote:
> Hi,
> I've a doubt on the best way (tm) to deal with HA in the case of services
> that are somehow proxies to some other resource (i.e.
> stateless in some sense).
>
> The problem seems to be that the clients need to know its identity
>
On Fri, Apr 15, 2011 at 7:51 AM, Florian Haas wrote:
> Andrew,
>
> the documentation states that unless your distro ships
> dlm_controld.pcmk, you should be installing cman and running Pacemaker
> on that. I presume this is because (at least on Fedora and RHEL), cman
> ships with the standard dlm_
Impossible to say without logs. Sounds strange though.
On Fri, Apr 15, 2011 at 7:17 AM, Tom Tux wrote:
> Hi
>
> I have a two node cluster (stonith enabled). On one node I tried
> stopping openais (/etc/init.d/openais stop), but this was hanging. So
> I killed all running corosync processes (kill
Andrew,
the documentation states that unless your distro ships
dlm_controld.pcmk, you should be installing cman and running Pacemaker
on that. I presume this is because (at least on Fedora and RHEL), cman
ships with the standard dlm_controld that now supports Pacemaker.
Now, for packagers on dist
Hi
I have a two node cluster (stonith enabled). On one node I tried
stopping openais (/etc/init.d/openais stop), but this was hanging. So
I killed all running corosync processes (killall -9 corosync).
Afterward, I started openais on this node again (rcopenais start).
After a few seconds, this node
hi adam,
On 14.04.2011 18:10, Adam Reiss wrote:
Hi Raoul,
We're trying to setup a HA SMTP Relay, so having pacemaker stop/start
the services as it passes the work over to the other machine, should
Postfix fail... Is there a better way to allow an HA SMTP relay?
when we're setting up a cluste
For mail, an alternative MX should do AFAIK.
Some kind of SNMP monitoring of the primary should be able to do the
notification in a standard way also.
-Carlos
Adam Reiss @ 14/04/2011 13:32 -0300 dixit:
I suppose there isn't any issue having it up all the time. We're
looking for the best way
Hi,
I've a doubt on the best way (tm) to deal with HA in the case of
services that are somehow proxies to some other resource (i.e.
stateless in some sense).
The problem seems to be that the clients need to know its identity
and location, which usually boils down to IP address.
Even though som
I suppose there isn't any issue having it up all the time. We're
looking for the best way to pass the traffic to the second node, should
the first one fail, then notify us that node 1 has failed...
-Original Message-
From: Carlos G Mendioroz [mailto:t...@huapi.ba.ar]
Sent: Thursday,
If it is an SMTP relay service, what's the problem with having it up all
the time ?
-Carlos
Adam Reiss @ 14/04/2011 13:10 -0300 dixit:
Hi Raoul,
We're trying to setup a HA SMTP Relay, so having pacemaker stop/start
the services as it passes the work over to the other machine, should
Postfix fa
Hi Raoul,
We're trying to setup a HA SMTP Relay, so having pacemaker stop/start
the services as it passes the work over to the other machine, should
Postfix fail... Is there a better way to allow an HA SMTP relay?
It's running under VMWare, having two different guests, on two different
hosts...
Andrew Beekhof writes:
Hi Andrew
FSR is file system replication, like Mysql multi-state resource, it replicates
the files from master to all the slaves in the cluster frame work.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.
Thank you!
On Thu, Apr 14, 2011 at 1:18 PM, Andrew Beekhof wrote:
> this should do it:
>
>
> maintenance-mode=true
> replace agents
> update cib
> crm resource cleanup name-of-resource-you-replaced
> maintenance-mode=true
>
> On Wed, Apr 13, 2011 at 9:58 PM, Evgeniy Ivanov
> wrote:
>> Hi,
>>
>>
On Thu, Apr 14, 2011 at 9:02 AM, rakesh k wrote:
> Hi All
>
> I had configure heartbeat with 2 node cluster and 7 resources
>
> The list of resources are Tomcat,apachehttpd,Mysql and FSR where mysql and
> FSR are multi-state resource.
>
> and i had given order and co-location constraints please fi
14.04.2011 12:18, Andrew Beekhof wrote:
> this should do it:
>
>
> maintenance-mode=true
> replace agents
> update cib
> crm resource cleanup name-of-resource-you-replaced
> maintenance-mode=true
Latter should be =false
Does it really help to replace RAs to ones with incompatible parameters
or
this should do it:
maintenance-mode=true
replace agents
update cib
crm resource cleanup name-of-resource-you-replaced
maintenance-mode=true
On Wed, Apr 13, 2011 at 9:58 PM, Evgeniy Ivanov wrote:
> Hi,
>
> I want to update cluster with new RAs and CIB. New CIB is incompatible
> with new RAs and
On Thu, Apr 14, 2011 at 10:49 AM, Andrew Beekhof wrote:
>>> I noticed that 4 of the master/slave resources will start right away but
>>> the
>>> 5 master/slave resource seems to take a minute or so and I am only running
>>> with one node.
>>> Is this expected?
>>
>> Probably, if the other 4 take
On Wed, Apr 13, 2011 at 7:19 PM, Bob Schatz wrote:
> Andrew,
> Thanks for responding. Comments inline with
>
> From: Andrew Beekhof
> To: The Pacemaker cluster resource manager
> Cc: Bob Schatz
> Sent: Tue, April 12, 2011 11:23:14 PM
> Subject: Re: [Pacemaker]
On Wed, Apr 13, 2011 at 3:05 PM, Florian Haas wrote:
> On 2011-04-13 11:06, Andrew Beekhof wrote:
>> On Sat, Mar 19, 2011 at 6:10 PM, Vladislav Bogdanov
>> wrote:
>>> Hi,
>>>
>>> just bumping this to be not forgotten.
>>
>> Actually I'd missed that this was a Pacemaker specific one and
>> therefo
I've pushed an alternate patch instead which should be more
comprehensive. Thanks for pointing out the problem though.
On Wed, Apr 13, 2011 at 12:06 PM, Dominik Klein wrote:
> Hi
>
> when the "ping" RA configured as
>
> primitive ping ocf:pacemaker:ping timeout="5s"
>
> it throws
>
> [: 5s: in
Hi All
I had configure heartbeat with 2 node cluster and 7 resources
The list of resources are Tomcat,apachehttpd,Mysql and FSR where mysql and
FSR are multi-state resource.
and i had given order and co-location constraints please find the crm
configuration for order and co-location
*colocation
22 matches
Mail list logo
