Re: [ClusterLabs] Antw: Re: Notification agent and Notification recipients

On Tue, 2017-08-08 at 17:40 +0530, Sriram wrote: > Hi Ulrich, > > > Please see inline. > > On Tue, Aug 8, 2017 at 2:01 PM, Ulrich Windl > wrote: > >>> Sriram schrieb am 08.08.2017 um > 09:30 in Nachricht >

Re: [ClusterLabs] Antw: Re: big trouble with a DRBD resource

On Tue, 2017-08-08 at 10:18 +0200, Ulrich Windl wrote: > >>> Ken Gaillot schrieb am 07.08.2017 um 22:26 in > >>> Nachricht > <1502137587.5788.83.ca...@redhat.com>: > > [...] > > Unmanaging doesn't stop monitoring a resource, it only prevents starting > > and stopping of the

Re: [ClusterLabs] big trouble with a DRBD resource

On Fri, Aug 04, 2017 at 06:20:22PM +0200, Lentes, Bernd wrote: > Hi, > > first: is there a tutorial or s.th. else which helps in understanding what > pacemaker logs in syslog and /var/log/cluster/corosync.log ? > I try hard to find out what's going wrong, but they are difficult to > understand,

Re: [ClusterLabs] Antw: Re: Antw: Re: big trouble with a DRBD resource

- On Aug 8, 2017, at 9:42 AM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: > > Maybe just be concrete with your questions, so it's much easier to provide > useful answers. > Which question is not concrete ? Bernd Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer

Re: [ClusterLabs] Antw: Re: Notification agent and Notification recipients

Hi Ulrich, Please see inline. On Tue, Aug 8, 2017 at 2:01 PM, Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > >>> Sriram schrieb am 08.08.2017 um 09:30 in > Nachricht >

Re: [ClusterLabs] Two nodes cluster issue

I read the corosync-qdevice (8) man page couple of times, and also the RH documentation at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/High_Availability_Add-On_Reference/s1-quorumdev-HAAR.html I think it will be great if you will be able to add some examples

Re: [ClusterLabs] big trouble with a DRBD resource

- On Aug 7, 2017, at 10:43 PM, kgaillot kgail...@redhat.com wrote: > > The logs are very useful, but not particularly easy to follow. It takes > some practice and experience, but I think it's worth it if you have to > troubleshoot cluster events often. I will give my best. > > It's on

Re: [ClusterLabs] big trouble with a DRBD resource

- On Aug 7, 2017, at 10:26 PM, kgaillot kgail...@redhat.com wrote: > > Unmanaging doesn't stop monitoring a resource, it only prevents starting > and stopping of the resource. That lets you see the current status, even > if you're in the middle of maintenance or what not. You can disable >

[ClusterLabs] Antw: Re: Notification agent and Notification recipients

>>> Sriram schrieb am 08.08.2017 um 09:30 in Nachricht

[ClusterLabs] Antw: Re: big trouble with a DRBD resource

>>> Ken Gaillot schrieb am 07.08.2017 um 22:26 in >>> Nachricht <1502137587.5788.83.ca...@redhat.com>: [...] > Unmanaging doesn't stop monitoring a resource, it only prevents starting > and stopping of the resource. That lets you see the current status, even > if you're in

[ClusterLabs] Antw: Re: Antw: Re: big trouble with a DRBD resource

>>> "Lentes, Bernd" schrieb am 07.08.2017 >>> um 17:19 in Nachricht <829544490.14807105.1502119148231.javamail.zim...@helmholtz-muenchen.de>: [...] > I'm not talking about LSB scripts as RA's, although that's possible: [...] Maybe just be concrete with your

Re: [ClusterLabs] Notification agent and Notification recipients

Hi Ken & Jan, In the cluster we have, there is only one resource running. Its a OPT-IN cluster with resource-stickiness set to INFINITY. Just to clarify my question, lets take a scenario where there are four nodes N1, N2, N3, N4 a. N1 comes up first, starts the cluster. b. N1 Checks that there