Re: [ClusterLabs] Coming in Pacemaker 2.1.3: multiple-active=stop_unexpected

On 08.04.2022 20:16, Ken Gaillot wrote: > Hi all, > > I'm hoping to have the first release candidate for Pacemaker 2.1.3 > available in a couple of weeks. > > One of the new features will be a new possible value for the "multiple- > active" resource meta-attribute, which specifies how the cluster

Re: [ClusterLabs] Antw: [EXT] SAP HANA monitor fails ‑ Error performing operation: No such device or address

Hi Ulrich, I set the cluster in maintenance mode due to the consistent logging of the error messages in the system log. Pacemaker has attempted to execute the monitor operation of the resource agent here. Is there a way to find out why pacemaker says 'No such device or address'? hanapopdb1-rsc_SA

[ClusterLabs] Coming in Pacemaker 2.1.3: multiple-active=stop_unexpected

Hi all, I'm hoping to have the first release candidate for Pacemaker 2.1.3 available in a couple of weeks. One of the new features will be a new possible value for the "multiple- active" resource meta-attribute, which specifies how the cluster should react if multiple instances of a resource are

Re: [ClusterLabs] Restarting parent of ordered clone resources on specific node causes restart of all resources in the ordering constraint on all nodes of the cluster

You can use 'kind' and 'symmetrical' to control order constraints. The default value for symmetrical is 'true' which means that in order to stop dummy1 , the cluster has to stop dummy1 & dummy2. Best Regards,Strahil Nikolov On Fri, Apr 8, 2022 at 15:29, ChittaNagaraj, Raghav wrote: Hel

Re: [ClusterLabs] SAP HANA monitor fails - Error performing operation: No such device or address

On Fri, 2022-04-08 at 17:17 +0800, Aj Revelino wrote: > Hello All, > I've a 2 node SAP Hana cluster (hanapodb1 and hanapodb2). Pacemaker > monitors the data replication between the primary and the secondary > node. The issue is that crm status shows that everything is okay but > the system log show

[ClusterLabs] Antw: [EXT] Restarting parent of ordered clone resources on specific node causes restart of all resources in the ordering constraint on all nodes of the cluster

Hi! Just two short notes: 1: I think "timeout > interval" does not make much sense. 2: I guess you configured the wrong type of clone ("meta interleave=true"?) (3: I don't know the "pcs" command) Regards, Ulrich >>> "ChittaNagaraj, Raghav" schrieb am 07.04.2022 um 22:48 in Nachricht > Hello

[ClusterLabs] Restarting parent of ordered clone resources on specific node causes restart of all resources in the ordering constraint on all nodes of the cluster

Hello Team, Hope you are doing well. I have a 4 node pacemaker cluster where I created clone dummy resources test-1, test-2 and test-3 below: $ sudo pcs resource create test-1 ocf:heartbeat:Dummy op monitor timeout="20" interval="10" clone $ sudo pcs resource create test-2 ocf:heartbeat:Dummy

[ClusterLabs] Antw: [EXT] SAP HANA monitor fails ‑ Error performing operation: No such device or address

"maintenance-mode=true"? Why? >>> Aj Revelino schrieb am 08.04.2022 um 11:17 in >>> Nachricht : > Hello All, > I've a 2 node SAP Hana cluster (hanapodb1 and hanapodb2). Pacemaker > monitors the data replication between the primary and the secondary node. > The issue is that crm status shows tha

[ClusterLabs] SAP HANA monitor fails - Error performing operation: No such device or address

Hello All, I've a 2 node SAP Hana cluster (hanapodb1 and hanapodb2). Pacemaker monitors the data replication between the primary and the secondary node. The issue is that crm status shows that everything is okay but the system log shows the following error log. *pacemaker-controld[3582]: notice: