Re: [ClusterLabs] pacemaker-2.0.x version support on “RHEL 7” OS

On Wed, 2021-03-10 at 07:15 +, S Sathish S wrote: > Hi Ken/Team, > > We are using pacemaker software from Clusterlab upstream with version > pacemaker 2.0.2 in our RHEL 7 system. So for fixing the CVE’s CVE- > 2020-25654 we don’t want to downgrade to lower version of pacemaker > 1.x hence we

Re: [ClusterLabs] pacemaker-2.0.x version support on “RHEL 7” OS

Hi, The same principles apply to both pcs and pacemaker (and most probably the whole cluster stack). Red Hat only supports the packages it provides, which is pcs-0.9 series in RHEL 7. Even if you manage to install ruby 2.2.0+ and python 3.6+ on RHEL 7 hosts and build and run pcs-0.10 on

Re: [ClusterLabs] pacemaker-2.0.x version support on “RHEL 7” OS

Hi Ken/Team, We are using pacemaker software from Clusterlab upstream with version pacemaker 2.0.2 in our RHEL 7 system. So for fixing the CVE’s CVE-2020-25654 we don’t want to downgrade to lower version of pacemaker 1.x hence we are trying to build latest pcs-0.10 version from upstream source

Re: [ClusterLabs] pacemaker-2.0.x version support on “RHEL 7” OS

Hi Sathish, You don't need to go through all that trouble. Red Hat backported the fix for that vulnerability to RHEL 7: https://access.redhat.com/errata/RHSA-2020:5453 The pacemaker-1.1.23-1.el7_9.1 packages available in RHEL 7.9 do not have the vulnerability. On Tue, 2021-03-09 at 05:09

Re: [ClusterLabs] pacemaker-2.0.x version support on “RHEL 7” OS

Hi Ken/Team, Thanks for the prompt response. pacemaker 2.0.2 version from upstream source we build and run on RHEL 7 with corosync-2.4.4 & pcs-0.9.169 software version. Due to CVE-2020-25654 high vulnerability is open on both the pacemaker 1.x and 2.x stream and fix is available in pacemaker

Re: [ClusterLabs] pacemaker-2.0.x version support on “RHEL 7” OS

On Fri, 2021-03-05 at 13:39 +, S Sathish S wrote: > Hi Team, > > pacemaker-2.0.x version support on “RHEL 7” OS. > > Thanks and Regards, > S Sathish S Hi, Red Hat only supports the packages it provides, which is the Pacemaker 1.1 series in RHEL 7. From an upstream perspective, you can

[ClusterLabs] pacemaker-2.0.x version support on “RHEL 7” OS

Hi Team, pacemaker-2.0.x version support on “RHEL 7” OS. Thanks and Regards, S Sathish S ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Pacemaker Fail Master-Master State

On Sun, 2021-02-21 at 12:56 +0300, İsmet BALAT wrote: > And this state can be. Master machine can down and anorher machine > can be new master. Then first machine can be online with master.Like > in video. This state, I cant fix because no internet. This machines > will use a offline project. All

Re: [ClusterLabs] Pacemaker Fail Master-Master State

And this state can be. Master machine can down and anorher machine can be new master. Then first machine can be online with master.Like in video. This state, I cant fix because no internet. This machines will use a offline project. All states have work successfully On 21 Feb 2021 Sun at 12:45

Re: [ClusterLabs] Pacemaker Fail Master-Master State

I am testing aşk scenarios because I will use real machines with pacemaker. Scenarios; 1- node1 master node2 slave Shutting node1, then node2 become master Successfully 2- node1 slave node2 master Shutting node2, then node1 become master Successfully 3- node1 slave node2 slave One node

Re: [ClusterLabs] Pacemaker Fail Master-Master State

My question is: Why you are pausing one VM?there is any specific scope in that?you should never have 2 master resources, pausing one vm could make unexpected behaviours. If you are testing failovers or simulated faults you must configure a fencing mechanism. Dont expect your cluster is working

Re: [ClusterLabs] Pacemaker Fail Master-Master State

Sorry, I am in +3utc and was sleeping. I will try first fix node, then start cluster. Thank you On 21 Feb 2021 Sun at 00:00 damiano giuliani wrote: > resources configured in a master/slave mode > If you got 2 masters something is not working right. You should never have > 2 node in master. >

Re: [ClusterLabs] Pacemaker Fail Master-Master State

resources configured in a master/slave mode If you got 2 masters something is not working right. You should never have 2 node in master. Disable pacemaker and corosync services to autostart on both nodes systemctl disable corosync Systemctl disable pacemaker You can start the faulty node using

Re: [ClusterLabs] Pacemaker Fail Master-Master State

I am not using fence. If I disable pacemaker,how node join cluster (for first example in video - master/slave changing)? So I need a check script for fault states :( And thank you for reply On 20 Feb 2021 Sat at 23:40 damiano giuliani wrote: > Hi, > > Have you correcly configure a working

Re: [ClusterLabs] Pacemaker Fail Master-Master State

Hi, Have you correcly configure a working fencing mechanism?without it you cant rely on a safe and consistent environment. My suggestion is to disable the autostart services (and so the autojoin into the cluster) on both nodes. if there is a fault you have to investigate before you rejoin the

Re: [ClusterLabs] Pacemaker 1.1 support period

Hello Ken, Thank you for reply. Best Regards, Andrei Andrei Zheregelia| Senior Software Engineer| DSR Corporation | E-mail: andrei.zherege...@dsr-corporation.com DSR logo

Re: [ClusterLabs] Pacemaker 1.1 support period

It ended with 1.1.24 in December. We will still accept pull requests that backport compatible fixes to the 1.1 branch, in case someone wants to make work easily available, but there will be no more releases, and we no longer test it. On Wed, 2021-02-03 at 18:47 +, Andrei Zheregelia wrote: >

[ClusterLabs] Pacemaker 1.1 support period

Hello, I would like to clarify support period for Pacemaker 1.1. Until which year it is planned to backport bugfixes into 1.1 branch and create releases? -- Best Regards, Andrei ___ Manage your subscription:

Re: [ClusterLabs] pacemaker 2.0.5 version pcs status resources command is not working

ker-2.0.5 --> https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2.0.5 <https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2.0.5> corosync-2.4.4 --> https://github.com/corosync/corosync/tree/v2.4.4 <https://github.com/coro

Re: [ClusterLabs] pacemaker 2.0.5 version pcs status resources command is not working

get pcs full list resource. >> >> >> >> *Latest Pacemaker version* : >> >> pacemaker-2.0.5 --> >> https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2.0.5 >> >> corosync-2.4.4 --> https://github.com/corosync/corosync/tree/v2.4.4 >&g

Re: [ClusterLabs] pacemaker 2.0.5 version pcs status resources command is not working

ll list resource. > > > > *Latest Pacemaker version* : > > pacemaker-2.0.5 --> > https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2.0.5 > > corosync-2.4.4 --> https://github.com/corosync/corosync/tree/v2.4.4 > > pcs-0.9.169 > > >

[ClusterLabs] pacemaker 2.0.5 version pcs status resources command is not working

://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2.0.5 corosync-2.4.4 --> https://github.com/corosync/corosync/tree/v2.4.4 pcs-0.9.169 [root@node2 ~]# pcs status resources [root@node2 ~]# Older Pacemaker version : pacemaker-2.0.2 --> https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2

[ClusterLabs] Pacemaker-2.0.5 build/install error

Hi Team, we are trying to building the latest 2.0.5 getting below error , can we know reason for the same https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2.0.5 $ ./autogen.sh $ ./configure --prefix /root/pacemaker/ Above two command sucessed without error. $ make

Re: [ClusterLabs] Pacemaker-2.0.5 build/install error

, 2021-01-29 at 10:36 +, S Sathish S wrote: > Hi Team, > > we are trying to building the latest 2.0.5 getting below error , can > we know reason for the same > > https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2.0.5 > > $ ./autogen.sh > $ ./configu

Re: [ClusterLabs] pacemaker alerts node_selector

I created https://github.com/ClusterLabs/pacemaker/pull/2241 to correct the schema mistake. On Wed, Nov 25, 2020 at 10:51 PM wrote: > > Hi, thank you for your reply. > > I tried it this way: > > >path="/usr/share/pace

Re: [ClusterLabs] pacemaker alerts node_selector

to select_nodes the section Thank you, Alfred -Ursprüngliche Nachricht- Von: Users Im Auftrag von Reid Wahl Gesendet: Donnerstag, 26. November 2020 05:30 An: Cluster Labs - All topics related to open-source clustering welcomed Betreff: Re: [ClusterLabs] pacemaker alerts node_selector

Re: [ClusterLabs] pacemaker alerts node_selector

/pacemaker/commit/bd451763 [2] https://github.com/ClusterLabs/pacemaker/blob/master/xml/alerts-2.9.rng [3] https://github.com/ClusterLabs/pacemaker/blob/master/xml/alerts-2.10.rng On Wed, Nov 25, 2020 at 9:31 AM wrote: > > Hi, I would like to trigger an external script, if something h

[ClusterLabs] pacemaker alerts node_selector

Hi, I would like to trigger an external script, if something happens on a specific node. In the documentation of alerts, i can see but whatever I put into the XML, it's not working... configuration>

[ClusterLabs] Pacemaker 2.0.5-rc3 now available

The third, and hopefully final, release candidate for Pacemaker 2.0.5 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.5-rc3 This release candidate largely consists of build and CI testing changes. There is not much that should affect most users

[ClusterLabs] Pacemaker 2.0.5-rc2 now available

The second release candidate for Pacemaker 2.0.5 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.5-rc2 The most important change in this release candidate is a fix for the ACL bypassing bug previously mentioned on this mailing list, and described in CVE

[ClusterLabs] Pacemaker 2.0.5-rc1 now available

Hi all, I am happy to announce that source code for the first release candidate for Pacemaker version 2.0.5 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.5-rc1 Highlights previously discussed on this list include supporting both number and integer

Re: [ClusterLabs] pacemaker and cluster hostname reconfiguration

Riccardo, > Only working way was to kill/reload corosync/pacemaker couple (I havent tried with reloading only pacemaker) on both nodes. I did a migration a long time ago, but haven't experienced any issues, probably because it was a part of a regular servers update (which includes reboot). Any

Re: [ClusterLabs] pacemaker and cluster hostname reconfiguration

Thanks Igor, I'm afraid I tried this path too although I did not mention in the issue. The procedure I followed was to add the "name" attribute to the node list in corosync.conf, with the current hostname, than reboot both nodes to start clean, than do the previously described procedure AND sed

Re: [ClusterLabs] pacemaker and cluster hostname reconfiguration

Hi Riccardo, As I see you have already handled the issue, but I would recommend using static node names in the corosync.conf instead of reference to hostname. I did so years ago and now I have no issues with hostname changes. e.g.: node { ring0_addr: 1.1.1.1 name: my.node

Re: [ClusterLabs] pacemaker and cluster hostname reconfiguration

Thank you for your suggestion Ken; I'm indeed on Centos7, but using hostnamectl set-hostname newHostname in place of hostname -f /etc/hostname didn't have any beneficial effect. As soon as I powered off one of the two nodes, the other one took the old hostnames back and drifted out of

Re: [ClusterLabs] pacemaker and cluster hostname reconfiguration

On Thu, 2020-10-01 at 10:40 +0200, Riccardo Manfrin wrote: > Ciao, > > I'm among the people that have to deal with with the in-famous two > nodes problem (http://www.beekhof.net/blog/2018/two-node-problems). > I am not sure if to open a bug for this.. so I'm first off reporting > on the list.. in

Re: [ClusterLabs] pacemaker and cluster hostname reconfiguration

Ciao, [TXT version] I'm among the people that have to deal with with the in-famous two nodes problem (http://www.beekhof.net/blog/2018/two-node-problems). I am not sure if to open a bug for this.. so I'm first off reporting on the list.. in the hope to get fast feedback. Problem statement I

[ClusterLabs] pacemaker and cluster hostname reconfiguration

Ciao, I'm among the people that have to deal with with the in-famous two nodes problem (http://www.beekhof.net/blog/2018/two-node-problems). I am not sure if to open a bug for this.. so I'm first off reporting on the list.. in the hope to get fast feedback. Problem statement I have a

Re: [ClusterLabs] Pacemaker not starting

Hello Please find below attached ss for cluster configuration file. On Fri, 25 Sep 2020, 8:46 pm Klaus Wenninger, wrote: > On 9/24/20 2:53 PM, Ambadas Kawle wrote: > > Hello Team > > > Please help me to solve this problem > > You have to provide us with some information about your > cluster

Re: [ClusterLabs] Pacemaker not starting

On 9/29/20 10:04 AM, Ambadas Kawle wrote: > Hello  > > Please find below attached ss for cluster configuration file. As Reid already pointed out your issue is probably a "pre pacemaker start thing". Regarding pacemaker-clusters running with cman there are probably otherswho can give you better

Re: [ClusterLabs] Pacemaker not starting

On 9/24/20 2:53 PM, Ambadas Kawle wrote: > Hello Team  > > > Please help me to solve this problem You have to provide us with some information about your cluster setup so that we can help. That is why we had asked you for the content of /etc/cluster/cluster.conf and the output of 'pcs config'.

Re: [ClusterLabs] Pacemaker not starting

Hello Team Please help me to solve this problem Thanks On Wed, 23 Sep 2020, 11:41 am Ambadas Kawle, wrote: > Hello All > > We have 2 node with Mysql cluster and we are not able to start pacemaker on > one of the node (slave node) > We are getting error "waiting for quorum... timed-out

Re: [ClusterLabs] Pacemaker not starting

What is the output of 'corosync-quorumtool -s' on both nodes ? What is your cluster's configuration : 'crm configure show' or 'pcs config' Best Regards, Strahil Nikolov В сряда, 23 септември 2020 г., 16:07:16 Гринуич+3, Ambadas Kawle написа: Hello All We have 2 node with Mysql

Re: [ClusterLabs] Pacemaker not starting

Please also share /etc/cluster/cluster.conf. Do you have `two_node="1" expected_votes="1"` in the element of cluster.conf? This is technically a cman startup issue. Pacemaker is waiting for cman to start first and form quorum through corosync first. On Wed, Sep 23, 2020 at 9:55 AM Strahil

[ClusterLabs] Pacemaker 1.1 series is now officially retired

Hi all, I had initially planned to make one last Pacemaker 1.1 series release at the end of this year. However at this point, we have not had a single backport to 1.1 since the last release, so I am happy to declare that 1.1.23 was the final release. :) We will still accept pull requests

Re: [ClusterLabs] Pacemaker/corosync with PostgreSQL 12

On Fri, 4 Sep 2020 10:55:31 +0200 Oyvind Albrigtsen wrote: > Add the "recovery.conf" parameters to postgresql.conf (except the > standby one) and touch standby.signal (which does the same thing). +1 > After you've verified that it's working and stop PostgreSQL you simply > rm standby.signal

Re: [ClusterLabs] Pacemaker/corosync with PostgreSQL 12

Add the "recovery.conf" parameters to postgresql.conf (except the standby one) and touch standby.signal (which does the same thing). After you've verified that it's working and stop PostgreSQL you simply rm standby.signal and the "recovery.conf" specific parameters, and the resource agent will

[ClusterLabs] Pacemaker/corosync with PostgreSQL 12

Hello, Please, can you provide example, explanation or give link to existing documentation - how to use pacemaker/corosync for HA Cluster for PostgreSQL 12.x? Problem is what in PostgreSQL 12 file "recovery.conf" is deprecated, not used now. -- WBR, Andrey Larionov

Re: [ClusterLabs] Pacemaker-remote: Connection to cluster failed: Transport endpoint is not connected

Probably I didn't configure pacemaker resource properly, now it's OK. --- crm configure show remote-db8-ca-3a-69-60-f4 node remote-db8-ca-3a-69-60-f4:remote \ attributes OpenStack-role=compute standby=off primitive remote-db8-ca-3a-69-60-f4 ocf:pacemaker:remote \ params

[ClusterLabs] Pacemaker-remote: Connection to cluster failed: Transport endpoint is not connected

Hi, guys, I'm running SLES12 sp3 and pacemaker-remote-1.1.16-4.8.x86_64, a few months ago, compute nodes of openstack are running well. But today when I setup a new compute node, it's said," - Aug 13 16:31:04 [43122] db8-ca-3a-69-60-f4 pacemaker_remoted: notice:

Re: [ClusterLabs] Pacemaker crashed and produce a coredump file

B0610011 crmd:error: >crm_ipc_read: Connection to lrmd failed > > > >> Hi, >> >> It looks like this is a bug that was fixed in later releases. The >`path` >> variable was a null pointer when it was passed to >> `systemd_unit_exec_with_unit` as the `u

Re: [ClusterLabs] Pacemaker crashed and produce a coredump file

On 7/29/20 10:39 AM, Reid Wahl wrote: > Hi, > > It looks like this is a bug that was fixed in later releases. The > `path` variable was a null pointer when it was passed to > `systemd_unit_exec_with_unit` as the `unit` argument. Commit 62a0d26a > <https://github.com/Cluster

[ClusterLabs] Pacemaker crashed and produce a coredump file

pointer when it was passed to > `systemd_unit_exec_with_unit` as the `unit` argument. Commit 62a0d26a > <https://github.com/ClusterLabs/pacemaker/commit/62a0d26a8f85fbcee9b56524ea3f1ae0171cbe52#diff-00b989f66499e2081134c17c06d2b359R201> > adds a null check to the `path` varia

Re: [ClusterLabs] Pacemaker crashed and produce a coredump file

Hi, It looks like this is a bug that was fixed in later releases. The `path` variable was a null pointer when it was passed to `systemd_unit_exec_with_unit` as the `unit` argument. Commit 62a0d26a <https://github.com/ClusterLabs/pacemaker/commit/62a0d26a8f85fbcee9b56524ea3f1ae0171cbe52#d

[ClusterLabs] Pacemaker crashed and produce a coredump file

RPM Version Information: corosync-2.3.4-7.el7_2.1.x86_64 pacemaker-1.1.12-22.el7.x86_64 Coredump file backtrace: ``` warning: .dynamic section for "/lib64/libk5crypto.so.3" is not at the expected address (wrong library or version mismatch?) Missing separate debuginfo for Try: yum

Re: [ClusterLabs] pacemaker startup problem

:  http://www.cdbaby.com/cd/gabrielebulfon Da: Reid Wahl A: Cluster Labs - All topics related to open-source clustering welcomed Data: 26 luglio 2020 12.25.20 CEST Oggetto: Re: [ClusterLabs] pacemaker startup problem Hmm. If it's reading PCMK_ipc_type and matching the server type to QB_IPC_SOCKET

Re: [ClusterLabs] pacemaker startup problem

:07 xstorage1 crmd[4315]: [ID 702911 daemon.error] error: >> Child process pengine exited (pid=4316, rc=100) >> Jul 26 11:39:07 xstorage1 crmd[4315]: [ID 702911 daemon.error] error: >> Could not recover from internal error >> Jul 26 11:39:07 xstorage1 heartbeat: [ID 996084 daemon.warn

Re: [ClusterLabs] pacemaker startup problem

n.warning] [4275]: > WARN: Managed /usr/libexec/pacemaker/crmd process 4315 exited with return > code 201. > > > > > *Sonicle S.r.l. *: http://www.sonicle.com > *Music: *http://www.gabrielebulfon.com > *Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon >

Re: [ClusterLabs] pacemaker startup problem

opics related to open-source clustering welcomed Data: 25 luglio 2020 0.46.52 CEST Oggetto: Re: [ClusterLabs] pacemaker startup problem On Fri, 2020-07-24 at 18:34 +0200, Gabriele Bulfon wrote: Hello, after a long time I'm back to run heartbeat/pacemaker/corosync on our XStreamOS/illumos distro. I re

Re: [ClusterLabs] pacemaker startup problem

: Gabriele Bulfon A: Cluster Labs - All topics related to open-source clustering welcomed Data: 26 luglio 2020 11.23.53 CEST Oggetto: Re: [ClusterLabs] pacemaker startup problem   Thanks, I ran it manually so I got those errors, running from service script it correctly set PCMK_ipc_type to socket.   But

Re: [ClusterLabs] pacemaker startup problem

: [ClusterLabs] pacemaker startup problem On Fri, 2020-07-24 at 18:34 +0200, Gabriele Bulfon wrote: Hello, after a long time I'm back to run heartbeat/pacemaker/corosync on our XStreamOS/illumos distro. I rebuilt the original components I did in 2016 on our latest release (probably a bit outdated, but I

Re: [ClusterLabs] pacemaker startup problem

On Fri, 2020-07-24 at 18:34 +0200, Gabriele Bulfon wrote: > Hello, > > after a long time I'm back to run heartbeat/pacemaker/corosync on our > XStreamOS/illumos distro. > I rebuilt the original components I did in 2016 on our latest release > (probably a bit outdated, but I want to start from

[ClusterLabs] pacemaker startup problem

Hello,   after a long time I'm back to run heartbeat/pacemaker/corosync on our XStreamOS/illumos distro. I rebuilt the original components I did in 2016 on our latest release (probably a bit outdated, but I want to start from where I left). Looks like pacemaker is having trouble starting up

Re: [ClusterLabs] pacemaker systemd resource

Thx Andrei, and to all of you guys for your time, i appreciate that! Yeah, it’s very sad to see that. Looks like a bug described here: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1869751 https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762 Well, for me no other way, but

Re: [ClusterLabs] Pacemaker Shutdown

Fencing could work. Thanks again Reid. From: Users on behalf of Reid Wahl Sent: 23 July 2020 10:10 To: Cluster Labs - All topics related to open-source clustering welcomed Subject: EXTERNAL: Re: [ClusterLabs] Pacemaker Shutdown Thanks for the clarification

Re: [ClusterLabs] Pacemaker Shutdown

ics related to open-source clustering > welcomed > *Subject:* EXTERNAL: Re: [ClusterLabs] Pacemaker Shutdown > > > On Tue, Jul 21, 2020 at 11:42 PM Harvey Shepherd < > harvey.sheph...@aviatnet.com> wrote: > > Hi All, > > I'm running Pacemaker 2.0.3 on a

Re: [ClusterLabs] Pacemaker Shutdown

Labs - All topics related to open-source clustering welcomed Subject: EXTERNAL: Re: [ClusterLabs] Pacemaker Shutdown On Tue, Jul 21, 2020 at 11:42 PM Harvey Shepherd mailto:harvey.sheph...@aviatnet.com>> wrote: Hi All, I'm running Pacemaker 2.0.3 on a two-node cluster, controll

Re: [ClusterLabs] Pacemaker Shutdown

On Tue, Jul 21, 2020 at 11:42 PM Harvey Shepherd < harvey.sheph...@aviatnet.com> wrote: > Hi All, > > I'm running Pacemaker 2.0.3 on a two-node cluster, controlling 40+ > resources which are a mixture of clones and other resources that are > colocated with the master instance of certain clones.

Re: [ClusterLabs] pacemaker systemd resource

On Wed, 2020-07-22 at 17:04 +0300, Andrei Borzenkov wrote: > > > On Wed, Jul 22, 2020 at 4:58 PM Ken Gaillot > wrote: > > On Wed, 2020-07-22 at 10:59 +0300, Хиль Эдуард wrote: > > > Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on > > > ubuntu 20 + 1 qdevice. I want to define

Re: [ClusterLabs] pacemaker systemd resource

On Wed, Jul 22, 2020 at 10:57 AM Andrei Borzenkov wrote: > 22.07.2020 12:46, Хиль Эдуард пишет: > > > > Hey, Andrei! Thanx for ur time! > > A-a-and there is no chance to do something? :( > > The pacemaker’s log below. > > > > Resource was started: > > ... > > Jul 22 12:38:36 node2.local

Re: [ClusterLabs] pacemaker systemd resource

22.07.2020 12:46, Хиль Эдуард пишет: > > Hey, Andrei! Thanx for ur time! > A-a-and there is no chance to do something? :(  > The pacemaker’s log below. >   Resource was started: ... > Jul 22 12:38:36 node2.local pacemaker-execd     [1721] (log_execute)      > info: executing - rsc:dummy.service

Re: [ClusterLabs] pacemaker systemd resource

On Wed, Jul 22, 2020 at 4:58 PM Ken Gaillot wrote: > On Wed, 2020-07-22 at 10:59 +0300, Хиль Эдуард wrote: > > Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on > > ubuntu 20 + 1 qdevice. I want to define new resource as systemd > > unit dummy.service : > > > > [Unit] > >

Re: [ClusterLabs] pacemaker systemd resource

On Wed, 2020-07-22 at 10:59 +0300, Хиль Эдуард wrote: > Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on > ubuntu 20 + 1 qdevice. I want to define new resource as systemd > unit dummy.service : > > [Unit] > Description=Dummy > [Service] > Restart=on-failure >

Re: [ClusterLabs] pacemaker systemd resource

Hey, Andrei! Thanx for ur time! A-a-and there is no chance to do something? :(  The pacemaker’s log below.     Jul 22 12:38:36 node2.local pacemaker-based     [1719] (cib_process_request)     info: Forwarding cib_apply_diff operation for section 'all' to all (origin=local/cibadmin/2) Jul 22

Re: [ClusterLabs] pacemaker systemd resource

Hi Klaus! Thank you for your attention, but isn’t work. I have added  Type=simple and there is no changes. I think problem not in service. As we can see from logs, the service is starting (Jul 21 15:53:42 node2.local dummy[9330]: hello world 1) but for the some reason pacemaker isn’t see it

[ClusterLabs] pacemaker systemd resource

Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on ubuntu 20 + 1 qdevice. I want to define new resource as systemd unit  dummy.service :   [Unit] Description=Dummy [Service] Restart=on-failure StartLimitInterval=20 StartLimitBurst=5 TimeoutStartSec=0 RestartSec=5

Re: [ClusterLabs] pacemaker systemd resource

On Wed, Jul 22, 2020 at 10:59 AM Хиль Эдуард wrote: > Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on ubuntu 20 > + 1 qdevice. I want to define new resource as systemd unit *dummy.service > *: > > [Unit] > Description=Dummy > [Service] > Restart=on-failure >

Re: [ClusterLabs] Pacemaker Shutdown

On Wed, Jul 22, 2020 at 9:42 AM Harvey Shepherd < harvey.sheph...@aviatnet.com> wrote: > Hi All, > > I'm running Pacemaker 2.0.3 on a two-node cluster, controlling 40+ > resources which are a mixture of clones and other resources that are > colocated with the master instance of certain clones.

Re: [ClusterLabs] pacemaker systemd resource

On 7/22/20 9:59 AM, Хиль Эдуард wrote: > Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on > ubuntu 20 + 1 qdevice. I want to define new resource as systemd > unit *dummy.service *: >   > [Unit] > Description=Dummy > [Service] Type=simple That could do the trick. Actually I thought

[ClusterLabs] Pacemaker Shutdown

Hi All, I'm running Pacemaker 2.0.3 on a two-node cluster, controlling 40+ resources which are a mixture of clones and other resources that are colocated with the master instance of certain clones. I've noticed that if I terminate pacemaker on the node that is hosting the master instances of

Re: [ClusterLabs] pacemaker together with ovirt or Kimchi ?

It won't make sense. oVirt has a built-in HA for Virtual Machines. Best Regards, Strahil Nikolov В събота, 11 юли 2020 г., 17:50:18 ч. Гринуич+3, Lentes, Bernd написа: Hi, i'm having a two node cluster with pacemaker and about 10 virtual domains as resources. It's running fine. I

[ClusterLabs] pacemaker together with ovirt or Kimchi ?

Hi, i'm having a two node cluster with pacemaker and about 10 virtual domains as resources. It's running fine. I configure/administrate everything with the crm shell. But i'm also looking for a web interface. I'm not much impressed by HAWK. Is it possible to use Kimchi or ovirt together with a

[ClusterLabs] Pacemaker 2.0.4-rc3 now available

As we've decided to go for another release candidate in that release cycle the third release candidate for Pacemaker 2.0.4 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.4-rc3 For details, please see the changelog: https://github.com/ClusterLabs

[ClusterLabs] Pacemaker 1.1.23-rc1, and the future of Pacemaker 1.1

Hi all, The first release candidate for Pacemaker 1.1.23, with selected backports from the 2.0.4 release, is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.23-rc1 We'll soon be 2 years from the release of Pacemaker 2.0.0, and I think it's time to move

[ClusterLabs] Pacemaker 2.0.4-rc2 now available

The second release candidate for Pacemaker 2.0.4 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.4-rc2 This has minor bug fixes and documentation improvements compared torc1. Improved parameter handling for RHCS-style fence-agents is complete now. Bugs

[ClusterLabs] Pacemaker 2.0.4-rc1 now available

Hi all, I am happy to announce that source code for the first release candidate for Pacemaker version 2.0.4 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.4-rc1 Some of the highlights of these release are: * 'shutdown-locks' This "fe

Re: [ClusterLabs] Pacemaker trades restart for migration on resource parameter change

"Ulrich Windl" writes: > schrieb am 13.03.2020 um 08:36 in Nachricht > <19666_1584085000_5e6b3808_19666_1044_1_87imj8vh90@lant.ki.iif.hu>: > >> A user noticed that after changing a non‑reloadable (unique) parameter >> of resource A in our cluster, A wasn't restarted as expected. On

[ClusterLabs] Pacemaker trades restart for migration on resource parameter change

Hi, A user noticed that after changing a non-reloadable (unique) parameter of resource A in our cluster, A wasn't restarted as expected. On closer inspection it turned out that the parameter change was coupled with a utilization change as well, which necessitated shuffling resources around. All

Re: [ClusterLabs] pacemaker certificate is not generated with SubjectAlternativeName

Dne 28. 02. 20 v 8:06 S Sathish S napsal(a): Hi Team, We have found that the Pacemaker certificate is not generated with SubjectAlternativeName. You are right, SubjectAlternativeName is not specified. Minor correction though, it's pcsd certificate, not pacemaker. Please find the general

[ClusterLabs] pacemaker certificate is not generated with SubjectAlternativeName

Hi Team, We have found that the Pacemaker certificate is not generated with SubjectAlternativeName. Please find the general guidelines : In case client certificates are required, verification of the client identity SHOULD use the first matching subjectAltName field of the client certificate

[ClusterLabs] pacemaker all the resource state are on stopped

Dear users, I have facing one strange issue on active active HA configuration. when any resource failed ,pacemaker is moving to another server and pcs status showing as per below. Cluster_eno4 (ocf::heartbeat:IPaddr2): Stopped testsrv1 Cluster_eno1 (ocf::heartbeat:IPaddr2):

Re: [ClusterLabs] pacemaker-controld getting respawned

ed in our system logs, Please find the >> pacemaker and corosync version installed on the system. >> >> Kindly let us know why we are getting below error on the system. >> >> corosync-2.4.4 à https://github.com/corosync/corosync/tree/v2.4.4 >> pacemaker-

Re: [ClusterLabs] pacemaker-controld getting respawned

the > pacemaker and corosync version installed on the system. > > Kindly let us know why we are getting below error on the system. > > corosync-2.4.4 à https://github.com/corosync/corosync/tree/v2.4.4 > pacemaker-2.0.2 à > https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-

[ClusterLabs] pacemaker-controld getting respawned

are getting below error on the system. corosync-2.4.4 --> https://github.com/corosync/corosync/tree/v2.4.4 pacemaker-2.0.2 --> https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2.0.2 [root@vmc0621 ~]# ps -eo pid,lstart,cmd | grep -iE 'corosync|pacemaker' | grep -v grep 2039 Wed Dec

[ClusterLabs] pacemaker won't start because duplicate node but can't remove dupe node because pacemaker won't start

I’ve asked this question on server fault and I’ll re-ask the whole thing here for posterity sake: https://serverfault.com/questions/995981/pacemaker-wont-start-because-duplicate-node-but-cant-remove-dupe-node-because

[ClusterLabs] pacemaker will not promote a drbd resource

Hi, I know this kind of problem has been posted numerous times but my google-fu doesn't seem to gather anything interesting and I'm really stuck. I have this 2 node cluster with multiple drbd resources in active/passive mode (only one primary allowed) and every time one primary drbd resource

Re: [ClusterLabs] Pacemaker 2.0.3-rc3 now available

On 14/11/19 14:54 +0100, Jan Pokorný wrote: > On 13/11/19 17:30 -0600, Ken Gaillot wrote: >> A longstanding pain point in the logs has been improved. Whenever the >> scheduler processes resource history, it logs a warning for any >> failures it finds, regardless of whether they are new or old,

Re: [ClusterLabs] Pacemaker 2.0.3-rc3 now available

On Thu, 2019-11-14 at 14:54 +0100, Jan Pokorný wrote: > On 13/11/19 17:30 -0600, Ken Gaillot wrote: > > This fixes some more minor regressions in crm_mon introduced in > > rc1. > > Additionally, after feedback from this list, the new output format > > options were shortened. The help is now: > >

Re: [ClusterLabs] Pacemaker 2.0.3-rc3 now available

On Wed, 13 Nov 2019 17:30:31 -0600 Ken Gaillot wrote: ... > A longstanding pain point in the logs has been improved. Whenever the > scheduler processes resource history, it logs a warning for any > failures it finds, regardless of whether they are new or old, which can > confuse anyone reading

Re: [ClusterLabs] Pacemaker 2.0.3-rc3 now available

On 13/11/19 17:30 -0600, Ken Gaillot wrote: > This fixes some more minor regressions in crm_mon introduced in rc1. > Additionally, after feedback from this list, the new output format > options were shortened. The help is now: > > Output Options: > --output-as=FORMAT Specify output format

<    1   2   3   4   5   6   7   >