On 03/03/2016 03:08 AM, Debabrata Pani wrote:
> Hi,
>
> In our deployment, due to some requirement, we need to do a :
> service network restart
>
> Due to this corosync crashes and the associated pacemaker processes crash
> as well.
>
> As per the last comment on this issue,
> ---
> Corosync
Hi,
In our deployment, due to some requirement, we need to do a :
service network restart
Due to this corosync crashes and the associated pacemaker processes crash
as well.
As per the last comment on this issue,
---
Corosync reacts oddly to that. It's better to use an iptables rule to
block
On 03/01/2016 04:33 PM, Rafał Sanocki wrote:
> but my score from pingd should be 200 because my config is
>
> node nodeA
> node nodeB
> primitive failover-ip1 ocf:pacemaker:node \
> op monitor interval="100s" \
> op start interval="0" timeout="2m" \
> op stop interval="0"
On 03/01/2016 11:24 PM, Sharat Joshi wrote:
> Hi List Folk,
>
> I am very new to Pacemaker and I am trying to build using sources.
> After successfully installing libqb and corosync under
> /disk1/software/libqb and /disk1/software/corosync and setting
>
> $ export
>
Hello List Folk ,
I have created a HA environment by using corosync and pacemaker.
Here is my ring status.
[~] # corosync-cfgtool -s
Printing ring status.
Local node ID 117918986
RING ID 0
id = 10.77.7.7
status = ring 0 active with no faults
Because some reason, I need
