Re: [ClusterLabs] service network restart and corosync

2016-03-30 Thread Jan Friesse
Hi Jan Friesse, Thank you for the update. I have responded inline. A few queries, as well. Regards, Debabrata Pani On 29/03/16 14:24, "Jan Friesse" wrote: Hi (Jan Friesse) I studied the issue mentioned in the github url. It looks the crash that I am talking about is

Re: [ClusterLabs] service network restart and corosync

2016-03-29 Thread Jan Friesse
Hi (Jan Friesse) I studied the issue mentioned in the github url. It looks the crash that I am talking about is slightly different from the one mentioned in the original issue. May be they are related, but I would like to Highlight my setup for ease. Three node cluster , one is in maintenance

Re: [ClusterLabs] service network restart and corosync

2016-03-29 Thread Debabrata Pani
Hi (Jan Friesse) I studied the issue mentioned in the github url. It looks the crash that I am talking about is slightly different from the one mentioned in the original issue. May be they are related, but I would like to Highlight my setup for ease. Three node cluster , one is in maintenance

Re: [ClusterLabs] service network restart and corosync

2016-03-03 Thread Jan Friesse
Hi, In our deployment, due to some requirement, we need to do a : service network restart What is exact reason for doing 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

Re: [ClusterLabs] service network restart and corosync

2016-03-02 Thread Klaus Wenninger
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

[ClusterLabs] service network restart and corosync

2016-03-02 Thread Debabrata Pani
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