Re: [ClusterLabs] ethernet link up/down - ?

On 07/02/2022 20:09, lejeczek via Users wrote: Hi guys How do you guys go about doing link up/down as a resource? many thanks, L. With simple tests I confirmed that indeed Linux - on my hardware at leat - can easily power down an eth link - if a @devel reads this: Is there an agent in

Re: [ClusterLabs] Redundant entries in log

Hi, Something is triggering a new transition. The most likely candidate is a low value for cluster-recheck-interval. Many years ago, a low cluster-recheck-interval was necessary to make certain things like failure-timeout more timely, but that has not been the case in a long time. It should be

[ClusterLabs] Redundant entries in log

Hello all, I am managing a cluster using pacemaker for high availability. I am parsing the logs for relevant information on the cluster health and the logs are full of the following: ``` Nov 29 09:17:41 esvm2 pacemaker-controld[2893]: notice: State transition S_IDLE -> S_POLICY_ENGINE Nov 29

[ClusterLabs] RemoteOFFLINE status, permanently

Hello, I deployed a Lustre cluster with 3 nodes (metadata) as pacemaker/corosync and 4 nodes as Remote Agents (for data). Initially all went well, I've set up MGS and MDS resources, checked failover and failback, remote agents were online. Then I tried to create a resource for OST on two nodes

Re: [ClusterLabs] ethernet link up/down - ?

On 16/02/2022 10:37, Klaus Wenninger wrote: On Tue, Feb 15, 2022 at 5:25 PM lejeczek via Users wrote: On 07/02/2022 19:21, Antony Stone wrote: > On Monday 07 February 2022 at 20:09:02, lejeczek via Users wrote: > >> Hi guys >> >> How do you guys go about

Re: [ClusterLabs] Pacemaker 2.1.7-rc2 now available

On 24/11/2023 09:18, Klaus Wenninger wrote: Hi all, Source code for the 2nd release candidate for Pacemaker version 2.1.7 is available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.7-rc2 This is primarily a bug fix release. See the ChangeLog or the link above for

Re: [ClusterLabs] ocf test IPaddr2

It would fail if the find interface function doesnt find the interface for the IP, but in this case you've specified netmask and nic, so it wont fail that test. You can use it with the ocf:pacemaker:ping agent which will fail if the IP is unreachable. Oyvind On 24/11/23 17:09 +, Fabrizio

Re: [ClusterLabs] make promoted follow promoted resource ?

On 26/11/2023 17:44, Andrei Borzenkov wrote: On 26.11.2023 12:32, lejeczek via Users wrote: Hi guys. With these: -> $ pcs resource status REDIS-6381-clone     * Clone Set: REDIS-6381-clone [REDIS-6381] (promotable):       * Promoted: [ ubusrv2 ]       * Unpromoted: [ ubusrv1 ubusrv3 ] -> $

Re: [ClusterLabs] make promoted follow promoted resource ?

On 26.11.2023 12:32, lejeczek via Users wrote: Hi guys. With these: -> $ pcs resource status REDIS-6381-clone   * Clone Set: REDIS-6381-clone [REDIS-6381] (promotable):     * Promoted: [ ubusrv2 ]     * Unpromoted: [ ubusrv1 ubusrv3 ] -> $ pcs resource status PGSQL-PAF-5433-clone   *

Re: [ClusterLabs] make promoted follow promoted resource ?

On 26/11/2023 12:20, Reid Wahl wrote: On Sun, Nov 26, 2023 at 1:32 AM lejeczek via Users wrote: Hi guys. With these: -> $ pcs resource status REDIS-6381-clone * Clone Set: REDIS-6381-clone [REDIS-6381] (promotable): * Promoted: [ ubusrv2 ] * Unpromoted: [ ubusrv1 ubusrv3 ] ->

Re: [ClusterLabs] make promoted follow promoted resource ?

On Sun, Nov 26, 2023 at 1:32 AM lejeczek via Users wrote: > > Hi guys. > > With these: > > -> $ pcs resource status REDIS-6381-clone > * Clone Set: REDIS-6381-clone [REDIS-6381] (promotable): > * Promoted: [ ubusrv2 ] > * Unpromoted: [ ubusrv1 ubusrv3 ] > > -> $ pcs resource status

Re: [ClusterLabs] make promoted follow promoted resource ?

On 26/11/2023 10:32, lejeczek via Users wrote: Hi guys. With these: -> $ pcs resource status REDIS-6381-clone   * Clone Set: REDIS-6381-clone [REDIS-6381] (promotable):     * Promoted: [ ubusrv2 ]     * Unpromoted: [ ubusrv1 ubusrv3 ] -> $ pcs resource status PGSQL-PAF-5433-clone   * Clone

[ClusterLabs] make promoted follow promoted resource ?

Hi guys. With these: -> $ pcs resource status REDIS-6381-clone   * Clone Set: REDIS-6381-clone [REDIS-6381] (promotable):     * Promoted: [ ubusrv2 ]     * Unpromoted: [ ubusrv1 ubusrv3 ] -> $ pcs resource status PGSQL-PAF-5433-clone   * Clone Set: PGSQL-PAF-5433-clone [PGSQL-PAF-5433]

Re: [ClusterLabs] [EXT] moving VM live fails?

On 24/11/2023 08:33, Windl, Ulrich wrote: Hi! So you have different CPUs in the cluster? We once had a similar situation with Xen using live migration: Migration failed, and the cluster "wasn't that smart" handling the situation. The solution was (with the help of support) to add some CPU

[ClusterLabs] ocf test IPaddr2

Hi all, is it normal that test is always passed even with a non used IP? [root@...~]# ping 10.10.62.87 PING 10.10.62.87 (10.10.62.87) 56(84) bytes of data. >From 10.10.62.83 icmp_seq=1 Destination Host Unreachable >From 10.10.62.83 icmp_seq=2 Destination Host Unreachable >From 10.10.62.83

[ClusterLabs] Pacemaker 2.1.7-rc2 now available

Hi all, Source code for the 2nd release candidate for Pacemaker version 2.1.7 is available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.7-rc2 This is primarily a bug fix release. See the ChangeLog or the link above for details. Everyone is encouraged to download,

Re: [ClusterLabs] [EXT] moving VM live fails?

Hi! So you have different CPUs in the cluster? We once had a similar situation with Xen using live migration: Migration failed, and the cluster "wasn't that smart" handling the situation. The solution was (with the help of support) to add some CPU flags masking in the VM configuration so that

Re: [ClusterLabs] [EXT] Re: Re: PAF / pgSQL fails after OS/system shutdown - FIX

Hi! I'm not using PgSQL in a cluster, but maybe gpSQL should provide some additional commands to help checking basic features, so that the RA does not need to know the internals. Kind regards, Ulrich -Original Message- From: Users On Behalf Of Jehan-Guillaume de Rorthais via Users

Re: [ClusterLabs] node orderly shutdown

On Tue, Nov 21, 2023 at 3:09 AM lejeczek via Users wrote: > > Hi guys. > > Having a node with a couple of _promoted_ resources - when such node is > os-shutdown in an orderly manner it seems that cluster takes a while. > By a "while" I mean longer than I'd expect a relatively simple 3-node

[ClusterLabs] node orderly shutdown

Hi guys. Having a node with a couple of _promoted_ resources - when such node is os-shutdown in an orderly manner it seems that cluster takes a while. By a "while" I mean longer than I'd expect a relatively simple 3-node cluster to move/promote a few _promoted_ resources: redis, postgresql,

Re: [ClusterLabs] non-existent attribute ?

On Sun, Nov 19, 2023 at 3:21 AM lejeczek via Users wrote: > > Hi guys. > > My 3-node cluster had one node absent for a long time and now when it's back > I cannot get _mariadb_ to start on that node. > ... > * MARIADB(ocf:heartbeat:galera): ORPHANED Stopped > ... > *

Re: [ClusterLabs] Typo in Clusters_from_Scratch

On Sun, Nov 19, 2023 at 2:45 PM Holger Schröder wrote: > > Hi all, > > i am just working through > https://clusterlabs.org/pacemaker/doc/2.1/Clusters_from_Scratch/singlehtml/. > there in section "7.7. Prefer One Node Over Another" the floating text says: > > In the location constraint below, we

[ClusterLabs] Typo in Clusters_from_Scratch

Hi all, i am just working through https://clusterlabs.org/pacemaker/doc/2.1/Clusters_from_Scratch/singlehtml/. there in section "7.7. Prefer One Node Over Another" the floating text says: In the location constraint below, we are saying the WebSite resource prefers the node pcmk-1 with a

[ClusterLabs] non-existent attribute ?

Hi guys. My 3-node cluster had one node absent for a long time and now when it's back I cannot get _mariadb_ to start on that node. ...     * MARIADB    (ocf:heartbeat:galera):     ORPHANED Stopped ...     * MARIADB-last-committed : 147     * MARIADB-safe-to-bootstrap  :

Re: [ClusterLabs] [EXT] Re: PAF / pgSQL fails after OS/system shutdown - FIX

On 13/11/2023 13:08, Jehan-Guillaume de Rorthais via Users wrote: On Mon, 13 Nov 2023 11:39:45 + "Windl, Ulrich" wrote: But shouldn't the RA check for that (and act appropriately)? Interesting. I'm open to discuss this. Below my thoughts so far. Why the RA should check that? There's

[ClusterLabs] moving VM live fails?

Hi guys. I have a resource which when asked to 'move' then it fails with:  virtqemud[3405456]: operation failed: guest CPU doesn't match specification: missing features: xsave but VM domain does not require (nor disable) the feature:       what even more interesting, _virsh_ migrate does

Re: [ClusterLabs] Corosync 3.1.8 is available at corosync.org!

thank you for your great job. Regards --- I'm SoCIaL, MayBe El 15/11/2023 a las 12:05 p. m., Jan Friesse escribió: I am pleased to announce the latest maintenance release of Corosync 3.1.8 is available immediately from the GitHub release section at

[ClusterLabs] Corosync 3.1.8 is available at corosync.org!

I am pleased to announce the latest maintenance release of Corosync 3.1.8 is available immediately from the GitHub release section at https://github.com/corosync/corosync/releases or our website at http://build.clusterlabs.org/corosync/releases/. This release contains mostly smaller bugfixes

Re: [ClusterLabs] PAF / pgSQL fails after OS/system shutdown - FIX

On Fri, 10 Nov 2023 20:34:40 +0100 lejeczek via Users wrote: > On 10/11/2023 18:16, Jehan-Guillaume de Rorthais wrote: > > On Fri, 10 Nov 2023 17:17:41 +0100 > > lejeczek via Users wrote: > > > > ... > >>> Of course you can use "pg_stat_tmp", just make sure the temp folder > >>> exists: > >>>

Re: [ClusterLabs] [EXT] Re: PAF / pgSQL fails after OS/system shutdown - FIX

On Mon, 13 Nov 2023 11:39:45 + "Windl, Ulrich" wrote: > But shouldn't the RA check for that (and act appropriately)? Interesting. I'm open to discuss this. Below my thoughts so far. Why the RA should check that? There's so many way to setup the system and PostgreSQL, where should the RA

Re: [ClusterLabs] [EXT] Re: PAF / pgSQL fails after OS/system shutdown - FIX

But shouldn't the RA check for that (and act appropriately)? -Original Message- From: Users On Behalf Of Jehan-Guillaume de Rorthais via Users Sent: Friday, November 10, 2023 1:13 PM To: lejeczek via Users Cc: Jehan-Guillaume de Rorthais Subject: [EXT] Re: [ClusterLabs] PAF / pgSQL

Re: [ClusterLabs] PAF / pgSQL fails after OS/system shutdown - FIX

On 10/11/2023 18:16, Jehan-Guillaume de Rorthais wrote: On Fri, 10 Nov 2023 17:17:41 +0100 lejeczek via Users wrote: ... Of course you can use "pg_stat_tmp", just make sure the temp folder exists: cat < /etc/tmpfiles.d/postgresql-part.conf # Directory for PostgreSQL temp stat

Re: [ClusterLabs] PAF / pgSQL fails after OS/system shutdown - FIX

On Fri, 10 Nov 2023 17:17:41 +0100 lejeczek via Users wrote: ... > > Of course you can use "pg_stat_tmp", just make sure the temp folder exists: > > > >cat < /etc/tmpfiles.d/postgresql-part.conf > ># Directory for PostgreSQL temp stat files > >d /var/run/postgresql/14-paf.pg_stat_tmp

Re: [ClusterLabs] PAF / pgSQL fails after OS/system shutdown - FIX

On 10/11/2023 13:13, Jehan-Guillaume de Rorthais wrote: On Fri, 10 Nov 2023 12:27:24 +0100 lejeczek via Users wrote: ... to share my "fix" for it - perhaps it was introduced by OS/packages (Ubuntu 22) updates - ? - as oppose to resource agent itself. As the logs point out - pg_stat_tmp -

Re: [ClusterLabs] PAF / pgSQL fails after OS/system shutdown - FIX

On Fri, 10 Nov 2023 12:27:24 +0100 lejeczek via Users wrote: ... > > > to share my "fix" for it - perhaps it was introduced by > OS/packages (Ubuntu 22) updates - ? - as oppose to resource > agent itself. > > As the logs point out - pg_stat_tmp - is missing and from > what I see it's only

Re: [ClusterLabs] PAF / pgSQL fails after OS/system shutdown - FIX

On 07/11/2023 17:57, lejeczek via Users wrote: hi guys Having 3-node pgSQL cluster with PAF - when all three systems are shutdown at virtually the same time then PAF fails to start when HA cluster is operational again. from status: ... Migration Summary:   * Node: ubusrv2 (2):     *

Re: [ClusterLabs] PAF / pgSQL fails after OS/system shutdown

On 07/11/2023 17:57, lejeczek via Users wrote: hi guys Having 3-node pgSQL cluster with PAF - when all three systems are shutdown at virtually the same time then PAF fails to start when HA cluster is operational again. from status: ... Migration Summary:   * Node: ubusrv2 (2):     *

[ClusterLabs] PAF / pgSQL fails after OS/system shutdown

hi guys Having 3-node pgSQL cluster with PAF - when all three systems are shutdown at virtually the same time then PAF fails to start when HA cluster is operational again. from status: ... Migration Summary:   * Node: ubusrv2 (2):     * PGSQL-PAF-5433: migration-threshold=100

[ClusterLabs] Pacemaker 2.1.7-rc1 now available

Hi all, Source code for the first release candidate for Pacemaker version 2.1.7 is available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.7-rc1 This is primarily a bug fix release. See the ChangeLog or the link above for details. Everyone is encouraged to download,

Re: [ClusterLabs] IPaddr2 clone deprecated

Thanks for clarify it. so right now there is now way have a simple LB for active/active resource on Pacemaker :/ Il giorno ven 20 ott 2023 alle ore 11:59 Oyvind Albrigtsen < oalbr...@redhat.com> ha scritto: > Hi Damiano, > > The clusterip functionality was removed from the kernel, and we havent

Re: [ClusterLabs] IPaddr2 clone deprecated

Hi Damiano, The clusterip functionality was removed from the kernel, and we havent currently been able to find a way to use the suggested replacement to perform the same kind of logic: https://wiki.nftables.org/wiki-nftables/index.php/Supported_features_compared_to_xtables#cluster Oyvind On

[ClusterLabs] IPaddr2 clone deprecated

Hi guys, im trying to create a IPaddr2 cloned resource for one of my project. i need some kind of simple but effective loadbalancer for my rabbitmq cluster managed by pacemaker. My current SO is Almalinux 8.6. seems IPaddr2 coned resource is not working / supported anymore, probably because

[ClusterLabs] Booth 1.1 is available at GitHub!

I am pleased to announce the latest maintenance release of Booth 1.1 is available immediately from GitHub at https://github.com/ClusterLabs/booth/releases as booth-1.1. Booth 1.1 has been released 7 long years after 1.0, so there are a huge number of changes and it is really hard to highlight

[ClusterLabs] fence-agents v4.13.1

ClusterLabs is happy to announce fence-agents v4.13.1, which is a bugfix release for v4.13.0. The source code is available at: https://github.com/ClusterLabs/fence-agents/releases/tag/v4.13.1 The most significant enhancements in this release are: - bugfixes and enhancements: - fence_azure_arm:

Re: [ClusterLabs] PCS ACL for the "pcs cluster stop" command

On 10/16/23 12:16, Klaus Wenninger wrote: On Fri, Oct 13, 2023 at 9:21 PM Reid Wahl > wrote: On Fri, Oct 13, 2023 at 12:19 PM Reid Wahl mailto:nw...@redhat.com>> wrote: > > On Fri, Oct 13, 2023 at 9:56 AM Roberto Rodrigos

Re: [ClusterLabs] PCS ACL for the "pcs cluster stop" command

Hi Roberto! On 10/13/23 10:13, Roberto Rodrigos wrote: good day! I use the configuration to create an ACL, it is shown below. How can I restrict access to the "pcs cluster stop" command for a user? There is way to restrict access to the `pcs cluster stop` command but you need to change

Re: [ClusterLabs] PCS ACL for the "pcs cluster stop" command

On Fri, Oct 13, 2023 at 9:21 PM Reid Wahl wrote: > On Fri, Oct 13, 2023 at 12:19 PM Reid Wahl wrote: > > > > On Fri, Oct 13, 2023 at 9:56 AM Roberto Rodrigos > wrote: > > > > > > good day! > > > I use the configuration to create an ACL, it is shown below. How can I > restrict access to the

Re: [ClusterLabs] Using cluster without fencing

пн, 16 окт. 2023 г. в 13:42, Andrei Borzenkov : > On Mon, Oct 16, 2023 at 9:28 AM Sergey Cherukhin > wrote: > > > > Hello! > > > > I use Postgresql+Pacemaker+Corosync 3 nodes cluster with 2 Postgresql > instances in synchronous replication mode on two high performance nodes and >

Re: [ClusterLabs] Using cluster without fencing

On Mon, Oct 16, 2023 at 9:28 AM Sergey Cherukhin wrote: > > Hello! > > I use Postgresql+Pacemaker+Corosync 3 nodes cluster with 2 Postgresql > instances in synchronous replication mode on two high performance nodes and > Pacemaker+Corosync on the third low performance node for quorum only. At

[ClusterLabs] Using cluster without fencing

Hello! I use Postgresql+Pacemaker+Corosync 3 nodes cluster with 2 Postgresql instances in synchronous replication mode on two high performance nodes and Pacemaker+Corosync on the third low performance node for quorum only. At the same time a SCADA HMI software is running on the high performance

Re: [ClusterLabs] PCS ACL for the "pcs cluster stop" command

On Fri, Oct 13, 2023 at 12:19 PM Reid Wahl wrote: > > On Fri, Oct 13, 2023 at 9:56 AM Roberto Rodrigos wrote: > > > > good day! > > I use the configuration to create an ACL, it is shown below. How can I > > restrict access to the "pcs cluster stop" command for a user? > > I don't think you can.

Re: [ClusterLabs] PCS ACL for the "pcs cluster stop" command

On Fri, Oct 13, 2023 at 9:56 AM Roberto Rodrigos wrote: > > good day! > I use the configuration to create an ACL, it is shown below. How can I > restrict access to the "pcs cluster stop" command for a user? I don't think you can. ACLs are implemented in Pacemaker; pcs simply provides an

[ClusterLabs] PCS ACL for the "pcs cluster stop" command

good day! I use the configuration to create an ACL, it is shown below. How can I restrict access to the "pcs cluster stop" command for a user? useradd rouser -m -G haclient useradd rwuser -m -G haclient passwd rwuser passwd rouser pcs acl enable pcs acl role create read-only description="Read

Re: [ClusterLabs] [EXT] Re: Re: Limit the number of resources starting/stoping in parallel possible?

Sorry for sending seemingly two messages on the same subject: I thought Outlook had "swallowed" the first messge when trying to convert from plain text to HTML... -Original Message- From: Users On Behalf Of Windl, Ulrich Sent: Wednesday, October 11, 2023 10:35 AM To: Cluster Labs - All

Re: [ClusterLabs] [EXT] Re: Limit the number of resources starting/stoping in parallel possible?

Hi! I'd wish there were some better mechanism that does not treat all resources being the same weight: Imagine you could assign a "score of heaviness" to each resource, and you could define a limit of the "total heaviness" in progress (either per node or clusterwide (thinking of shared

Re: [ClusterLabs] [EXT] Limit the number of resources starting/stoping in parallel possible?

Hi! I wonder (thinking "utilization"): The types of resources are quite different (like a VM vs. an IP address), so wouldn't it make sense to be able to define classes of resources that you can limit (or not) regarding parallel execution? The current utilization mechanism cannot be used,

[ClusterLabs] resource-agents v4.13.0

ClusterLabs is happy to announce resource-agents v4.13.0. Source code is available at: https://github.com/ClusterLabs/resource-agents/releases/tag/v4.13.0 The most significant enhancements in this release are: - bugfixes and enhancements: - findif.sh: dont use table parameter as it returns no

Re: [ClusterLabs] Upgrade to OLE8 + Pacemaker

Hi Qusay, please, find respones in-line. On 10/6/23 14:53, Jibrail, Qusay (GfK) via Users wrote: Hi, May I get an answer please? Kind regards, *––* *Qusay Jibrail* Senior Infrastructure Engineer – Linux | GfK IT Services GfK – an NIQ company |The Netherlands Krijgsman 22-25 | Amstelveen |

Re: [ClusterLabs] crm fails with: Failed to find "console" handler in logger "crmsh.main"

Hi Xin, Thanks for your quick response. I also doubt that the Python code in /usr/local/bin/crm (that’s the location in my case) has changed. Perhaps it’s enough if I submit the md5sum here instead of pasting the entire file: it’s 2bcdfe720f28061a4f71fe7d8d114220 (49 lines). I don't know

[ClusterLabs] fence-agents v4.13.0

ClusterLabs is happy to announce fence-agents v4.13.0. The source code is available at: https://github.com/ClusterLabs/fence-agents/releases/tag/v4.13.0 The most significant enhancements in this release are: - new fence agents: - fence_eaton_ssh - bugfixes and enhancements: - fence_aliyun:

Re: [ClusterLabs] crm fails with: Failed to find "console" handler in logger "crmsh.main"

Is your bin/crm the same with this https://github.com/ClusterLabs/crmsh/blob/4.4.0/bin/crm? From: christian2 Sent: Tuesday, October 10, 2023 3:10 PM To: Xin Liang Cc: users@clusterlabs.org Subject: Re: [ClusterLabs] crm fails with: Failed to find "console"

Re: [ClusterLabs] crm fails with: Failed to find "console" handler in logger "crmsh.main"

Hi Christian Please paste your /usr/sbin/crm, I doubt something broken with this file. BTW, what's the last git commit number of crmsh that Debian Bookworm uses? From: Users on behalf of christian2 Sent: Monday, October 9, 2023 9:30 PM To:

[ClusterLabs] crm fails with: Failed to find "console" handler in logger "crmsh.main"

Hello members, I have upgraded from crm 4.2.0 to 4.4.0 as part of a Debian upgrade from Bullseye to Bookworm. Unfortunately, “crm -d status” now fails with the error message indicated in the title and with the following stackdump. Since all indicated source files belong to the Debian package

Re: [ClusterLabs] Upgrade to OLE8 + Pacemaker

Hi, May I get an answer please? Kind regards, –– Qusay Jibrail Senior Infrastructure Engineer – Linux | GfK IT Services GfK – an NIQ company | The Netherlands Krijgsman 22-25 | Amstelveen | 1186 DM T: +31 88 435 1232 | M: +31 628 927 686

Re: [ClusterLabs] Syncronous primary doesn't switch to async mode on replica power off

Approach with alert agent is working now. It requires to call "pcs resource cleanup" by root using sudo, add "sleep 120" before calling pcs utility in alert agent script and increase alert agent timeout adequately. But I don't like this workaround, it takes too long a time to switch primary node

Re: [ClusterLabs] Syncronous primary doesn't switch to async mode on replica power off

On Fri, Oct 6, 2023 at 8:46 AM Sergey Cherukhin wrote: > Hello! > > I used Microsoft Outlook to send this message and it was sent in the wrong > format. I'm sorry. I won't do it again. > > I use Postgresql+Pacemaker+Corosync cluster with 2 Postgresql instances in > synchronous replication mode.

[ClusterLabs] Syncronous primary doesn't switch to async mode on replica power off

Hello! I used Microsoft Outlook to send this message and it was sent in the wrong format. I'm sorry. I won't do it again. I use Postgresql+Pacemaker+Corosync cluster with 2 Postgresql instances in synchronous replication mode. Parameter “rep_mode” is set to "sync", and when I shut down the

Re: [ClusterLabs] Upgrade to OLE8 + Pacemaker

Hi Tomas, Ok.. it is getting little bit complicated. What about this approach: * pcs cluster stop “server3”, do upgrade to OLE8 + update pacemaker, corosync and pcs, check postfix is working, wait 1 day. * pcs cluster stop “server4”, do upgrade to OLE8 + update pacemaker, corosync

[ClusterLabs] resource-agents v4.13.0 rc1

ClusterLabs is happy to announce resource-agents v4.13.0 rc1. Source code is available at: https://github.com/ClusterLabs/resource-agents/releases/tag/v4.13.0rc1 The most significant enhancements in this release are: - bugfixes and enhancements: - iSCSILogicalUnit/iSCSITarget: add support for

Re: [ClusterLabs] Upgrade to OLE8 + Pacemaker

Dne 03. 10. 23 v 16:24 Jibrail, Qusay (GfK) via Users napsal(a): Hi Reid, Thank you for the answer. So my plan will be: * pcs config backup  /root/"Server Name" * create a backup of /etc/corosync/ * create a backup of /etc/postfix * pcs cluster stop “server3” àjust to do the failover

Re: [ClusterLabs] Upgrade to OLE8 + Pacemaker

Hi Reid, Thank you for the answer. So my plan will be: * pcs config backup /root/"Server Name" * create a backup of /etc/corosync/ * create a backup of /etc/postfix * pcs cluster stop “server3” --> just to do the failover to server4. The command pcs cluster stop “server3” will

Re: [ClusterLabs] How to output debug messages in the log file?

On Tue, 2023-10-03 at 18:19 +0800, Jack via Users wrote: > I wrote a resource file Stateful1 in /lib/ocf/resources/pacemaker on > Ubuntu 22.04. It didn't working. So I wrote ocf_log debug "hello > world" in the file Stateful1. But it didn't output debug messages. > How can I output debug

[ClusterLabs] How to output debug messages in the log file?

I wrote a resource file Stateful1 in /lib/ocf/resources/pacemaker on Ubuntu 22.04. It didn't working. So I wrote ocf_log debug "hello world" in the file Stateful1. But it didn't output debug messages. How can I output debug messages?___ Manage your

Re: [ClusterLabs] Upgrade to OLE8 + Pacemaker

On Mon, Oct 2, 2023 at 10:51 PM Jibrail, Qusay (GfK) via Users < users@clusterlabs.org> wrote: > Hello, > > > > I am aiming for upgrading one of the cluster node to OLE8 (current version > OLE7) and test if postfix is working fine. > > If yes then upgrade the second node to OLE8. > > > > My

[ClusterLabs] Upgrade to OLE8 + Pacemaker

Hello, I am aiming for upgrading one of the cluster node to OLE8 (current version OLE7) and test if postfix is working fine. If yes then upgrade the second node to OLE8. My questions: Will Pacemaker configuration works after the upgrade? Do I need to make any changes before or after the upgrade

Re: [ClusterLabs] Mutually exclusive resources ?

On 9/27/23 16:58, Ken Gaillot wrote: On Wed, 2023-09-27 at 16:24 +0200, Adam Cecile wrote: On 9/27/23 16:02, Ken Gaillot wrote: On Wed, 2023-09-27 at 15:42 +0300, Andrei Borzenkov wrote: On Wed, Sep 27, 2023 at 3:21 PM Adam Cecile wrote: Hello, I'm struggling to understand if it's

[ClusterLabs] Postgresql+Pacemaker+Corosync unexpected behavior

Hello! I have configured Postgresql+Pacemaker+Corosync with 3 nodes, 2 of them for Postgresql HA cluster and one as a witness. 3 nodes configured 4 resource instances configured Online: [ witness wizard1 wizard2 ] Full list of resources: ClusterIP (ocf::heartbeat:IPaddr2): Started wizard1

[ClusterLabs] Postgresql+Pacemaker+Corosync unexpected behavior

Hello! I have configured Postgresql+Pacemaker+Corosync with 3 nodes, 2 of them for Postgresql HA cluster and one as a witness. 3 nodes configured 4 resource instances configured Online: [ witness wizard1 wizard2 ] Full list of resources: ClusterIP (ocf::heartbeat:IPaddr2): Started wizard1

[ClusterLabs] ACL activation not working in the cluster

Hello, I'm continuing my journey into clustering learning and testing a configuration involving ACL setup for cluster management. However, enabling this option, both through Hawk and using the crmsh command: `crm configure property enable-acl=true` seems not to be working. The Access Control

Re: [ClusterLabs] Unable to start Apache resource

On Fri, Sep 29, 2023 at 12:51 AM Bartosz Kaczyński wrote: > > Reid Wahl writes: > > > On Tue, Sep 19, 2023 at 9:10 AM Bartosz Kaczyński > > wrote: > >> > >> Greetings, > >> > >> I am facing an issue with launching a primitive resource in a two-node > >> Pacemaker/Corosync cluster. I have set

Re: [ClusterLabs] Unable to start Apache resource

Reid Wahl writes: > On Tue, Sep 19, 2023 at 9:10 AM Bartosz Kaczyński > wrote: >> >> Greetings, >> >> I am facing an issue with launching a primitive resource in a two-node >> Pacemaker/Corosync cluster. I have set up a lab environment based on the >> guidelines from the "Say Goodbye to

Re: [ClusterLabs] Mutually exclusive resources ?

On Wed, 2023-09-27 at 16:24 +0200, Adam Cecile wrote: > On 9/27/23 16:02, Ken Gaillot wrote: > > On Wed, 2023-09-27 at 15:42 +0300, Andrei Borzenkov wrote: > > > On Wed, Sep 27, 2023 at 3:21 PM Adam Cecile > > > wrote: > > > > Hello, > > > > > > > > > > > > I'm struggling to understand if it's

Re: [ClusterLabs] Mutually exclusive resources ?

On 9/27/23 16:02, Ken Gaillot wrote: On Wed, 2023-09-27 at 15:42 +0300, Andrei Borzenkov wrote: On Wed, Sep 27, 2023 at 3:21 PM Adam Cecile wrote: Hello, I'm struggling to understand if it's possible to create some kind of constraint to avoid two different resources to be running on the same

Re: [ClusterLabs] Mutually exclusive resources ?

On Wed, 2023-09-27 at 15:42 +0300, Andrei Borzenkov wrote: > On Wed, Sep 27, 2023 at 3:21 PM Adam Cecile > wrote: > > Hello, > > > > > > I'm struggling to understand if it's possible to create some kind > > of constraint to avoid two different resources to be running on the > > same host. > >

Re: [ClusterLabs] Mutually exclusive resources ?

On Wed, Sep 27, 2023 at 3:21 PM Adam Cecile wrote: > > Hello, > > > I'm struggling to understand if it's possible to create some kind of > constraint to avoid two different resources to be running on the same host. > > Basically, I'd like to have floating IP "1" and floating IP "2" always being

Re: [ClusterLabs] Mutually exclusive resources ?

Hi, Probably utilization attributes may help with that. Try to add f.e. 'ip' utilization attrubute with value '1' to both nodes, and then add the same to VIP resources. Adam Cecile 27 сентября 2023 г. 14:21:05 написал: Hello, I'm struggling to understand if it's possible to create some

[ClusterLabs] Mutually exclusive resources ?

Hello, I'm struggling to understand if it's possible to create some kind of constraint to avoid two different resources to be running on the same host. Basically, I'd like to have floating IP "1" and floating IP "2" always being assigned to DIFFERENT nodes. Is that something possible ?

[ClusterLabs] kronosnet v1.28 released

All, We are pleased to announce the general availability of kronosnet v1.28 kronosnet (or knet for short) is the new underlying network protocol for Linux HA components (corosync), that features the ability to use multiple links between nodes, active/active and active/passive link failover

Re: [ClusterLabs] [ClusterLabs Developers] kronosnet v1.27 released

This release unfortunately fails to build on i686. I am prepping 1.28 with just the build fix. If you are in a hurry you can grab it here: https://github.com/kronosnet/kronosnet/pull/417/files Cheers Fabio On 26/09/2023 14.43, Fabio M. Di Nitto wrote: All, We are pleased to announce the

[ClusterLabs] kronosnet v1.27 released

All, We are pleased to announce the general availability of kronosnet v1.27 kronosnet (or knet for short) is the new underlying network protocol for Linux HA components (corosync), that features the ability to use multiple links between nodes, active/active and active/passive link failover

Re: [ClusterLabs] Unable to start Apache resource

On Mon, Sep 25, 2023 at 4:50 PM Reid Wahl wrote: > > On Tue, Sep 19, 2023 at 9:10 AM Bartosz Kaczyński > wrote: > > > > Greetings, > > > > I am facing an issue with launching a primitive resource in a two-node > > Pacemaker/Corosync cluster. I have set up a lab environment based on the > >

Re: [ClusterLabs] Unable to start Apache resource

On Tue, Sep 19, 2023 at 9:10 AM Bartosz Kaczyński wrote: > > Greetings, > > I am facing an issue with launching a primitive resource in a two-node > Pacemaker/Corosync cluster. I have set up a lab environment based on the > guidelines from the "Say Goodbye to Downtime with SUSE Linux Enterprise >

[ClusterLabs] announcement: schedule for resource-agents release 4.13.0

Hi, This is a tentative schedule for resource-agents v4.13.0: 4.13.0-rc1: Oct 4. 4.13.0: Oct 11. The storage-mon resource agent has got a new daemon mode that can be enabled to avoid child processes remaining stuck after I/O has been unresponsive, so make sure to give it some additional

[ClusterLabs] Unable to start Apache resource

Greetings, I am facing an issue with launching a primitive resource in a two-node Pacemaker/Corosync cluster. I have set up a lab environment based on the guidelines from the "Say Goodbye to Downtime with SUSE Linux Enterprise Server (Repeat)" [1] course. In my lab environment, I am using

Re: [ClusterLabs] Limit the number of resources starting/stoping in parallel possible?

Hi Ken, that sounds good. I'll test the option. Perhaps we'll change something on the resource type, too. Our systemd Resource do some things with docker containers (start, stop ...). We need the real status of the dockerized application (perhaps via a REST Endpoint), up & running does not

Re: [ClusterLabs] Limit the number of resources starting/stoping in parallel possible?

Hi Antony, all Services must be stopped if the VIP moves away. There is a really complex structure behind the Services. The Services cannot start without VIP. greets Steffen Von: Users im Auftrag von Ken Gaillot Gesendet: Montag, 18. September 2023 16:36 An:

Re: [ClusterLabs] pacemaker-remote

On Thu, 2023-09-14 at 18:28 +0800, Mr.R via Users wrote: > Hi all， > > In Pacemaker-Remote 2.1.6, the pacemaker package is required > for guest nodes and not for remote nodes. Why is that? What does > pacemaker do? > After adding guest node, pacemaker package does not seem to be > needed.

Re: [ClusterLabs] Limit the number of resources starting/stoping in parallel possible?

On Mon, 2023-09-18 at 14:24 +, Knauf Steffen wrote: > Hi, > > we have multiple Cluster (2 node + quorum setup) with more then 100 > Resources ( 10 x VIP + 90 Microservices) per Node. > If the Resources are stopped/started at the same time the Server is > under heavy load, which may result

Re: [ClusterLabs] Limit the number of resources starting/stoping in parallel possible?

On Monday 18 September 2023 at 16:24:02, Knauf Steffen wrote: > Hi, > > we have multiple Cluster (2 node + quorum setup) with more then 100 > Resources ( 10 x VIP + 90 Microservices) per Node. If the Resources are > stopped/started at the same time the Server is under heavy load, which may >

[ClusterLabs] Limit the number of resources starting/stoping in parallel possible?

Hi, we have multiple Cluster (2 node + quorum setup) with more then 100 Resources ( 10 x VIP + 90 Microservices) per Node. If the Resources are stopped/started at the same time the Server is under heavy load, which may result into timeouts and an unresponsive server. We configured some Ordering

<    1   2   3   4   5   6   7   8   9   10   >