On 02/11/2011 07:58 PM, paul harford wrote:
> Hi Florian
> i had seen apache 2 in one of the pacemaker mails, it may have been a
> typo but i just wanted to check, thanks for your help
Welcome. And I noticed I left out a "2" in the dumbest of places in my
original reply, but I trust you figured th
On 02/11/2011 06:47 PM, Raoul Bhatia [IPAX] wrote:
>> Additionally I want the virtual-IP to be moved if upstream-connectivity
>> of a node is broken. Therefore I used ping as below:
>>
>> primitive extip ocf:heartbeat:IPaddr \
>> params ip="11.222.32.161" \
>> op monitor interval="3
Hi Florian
i had seen apache 2 in one of the pacemaker mails, it may have been a typo
but i just wanted to check, thanks for your help
paul
On 11 February 2011 11:00, Florian Haas wrote:
> On 2011-02-11 11:53, paul harford wrote:
> > Hi Guys
> > Could anyone tell me what the difference betwee
hi,
On 02/11/2011 05:55 PM, Klaus Darilion wrote:
>> if the clone'd resource properly synchronizes by itself, you only need
>> to migrate the (public) service ip address. a colocation rule will
>> achieve that.
>
> fine
>
>> basic clone setup:
>> primitive extip ocf:heartbeat:IPaddr2 \
>>
Hi Raoul!
Am 11.02.2011 16:13, schrieb Raoul Bhatia [IPAX]:
> On 02/11/2011 03:07 PM, Klaus Darilion wrote:
...
>> Is there some protection in pacemaker to not endlessly trying to restart
>> such a broken service?
>>
>> Or, how should pacemaker behave if Kamailio on the active node crashes.
>> Sha
hi,
On 02/11/2011 03:07 PM, Klaus Darilion wrote:
...
> If everything is fine, then Kamailio should run on both servers.
>
> But for example how should the cluster behave if e.g. Kamailio crashes
> and restarting by pacemaker again leads to crashes (e.g. Kamailio has DB
> connectivity problems or
Am 11.02.2011 11:27, schrieb Raoul Bhatia [IPAX]:
> hi,
>
> On 02/09/2011 03:04 PM, Klaus Darilion wrote:
> ...
>>
>>
>> server1 server2
>> ip1ip2
>> <-virtual-IP--->
>>
> ...
>> Kamailio should always be
On 2011-02-11 11:53, paul harford wrote:
> Hi Guys
> Could anyone tell me what the difference between (resources)
>
> IPaddr and IPaddr2
IPaddr uses ifconfig and is meant to be portable across platforms,
IPaddr uses ip, has more features, but is Linux only.
> and
>
> Apache and Apache2
Huh?
Hi Guys
Could anyone tell me what the difference between (resources)
IPaddr and IPaddr2
and
Apache and Apache2
Is there any advantage to using the *2 resources over the other ones ?
Thanks :-)
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.or
hi,
On 02/09/2011 03:04 PM, Klaus Darilion wrote:
...
>
>
> server1 server2
> ip1ip2
> <-virtual-IP--->
>
...
> Kamailio should always be running on both servers. Replication of
> Registrations is done on
> On: Fri, 11 Feb 2011 01:54:04 +0100, Lars Ellenberg worte:
> On Wed, Feb 09, 2011 at 02:48:52PM +0100, Stephan-Frank Henry wrote:
> > My scenario:
> > Acive/Passive 2 node cluster (serverA & serverB) with Corosync, DRBD &
> PGSQL.
> > The resources are configured as Master/Slave and sofar it is f
On 2011-02-11 09:16, Uwe Schmeling wrote:
> Hi,
>
> I'm just migrating my recent mon/heartbeat configuration to pacemaker.
> The point of interest is the webservice behavior. Before the monitor
> checked if the service failed twice within 20 sec, switch to other node
> was initiated if this happen
On 02/09/11 22:44, Raoul Bhatia [IPAX] wrote:
> hi,
>
> On 09.02.2011 08:43, u.schmel...@online.de wrote:
>> I don't use ocf:heartbeat:apache because of my special configuration:
>>
>> apache is active on both nodes, the access is via haproxy, we have an
>> url http://localhost:80 which accesses th
Hi,
I'm just migrating my recent mon/heartbeat configuration to pacemaker.
The point of interest is the webservice behavior. Before the monitor
checked if the service failed twice within 20 sec, switch to other node
was initiated if this happens. Now I'm trying to configuring the same
behavior usi
14 matches
Mail list logo
