Hi all,
The first release candidate for Pacemker 2.1.8 is available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.8-rc1
This release has a number of new features and bugfixes, along with
deprecations of (mostly undocumented and/or broken) some obscure
features.
Two
On Thu, 2024-02-08 at 10:12 +0800, hywang via Users wrote:
> hello, everyone,
> I want to make a node fenced or the cluster stopped after a
> resource start failed 3 times, how to make the resource configure to
> achive it?
> Thanks!
>
The current design doesn't allow it. You can set
hello, everyone,
I want to make a node fenced or the cluster stopped after a
resource start failed 3 times, how to make the resource configure to achive it?
Thanks!___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
Hi all,
Source code for Pacemaker version 2.1.7 is available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.7
This is primarily a bug fix release. See the ChangeLog or the link
above for details.
Many thanks to all contributors of source code to this release,
including
Hi all,
Source code for the fourth (and very likely final) release candidate
for Pacemaker version 2.1.7 is available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.7-rc4
This release candidate fixes a newly found regression that was
introduced in rc1.
This is probably
Hi all,
Source code for the third (and likely final) release candidate for
Pacemaker version 2.1.7 is available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.7-rc3
This release candidate fixes a couple issues introduced in rc1. See the
ChangeLog or the link above
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
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
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
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.
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. Can I not install it here?
After testing, remote nodes can be offline, but
On Thu, 2023-07-20 at 12:43 +0530, Priyanka Balotra wrote:
> What I mainly want to understand is that:
> - why "fatal failure" is coming
The logs so far don't show that. The earliest sign is:
Jul 17 14:18:20.085 FILE-6 pacemaker-fenced[19411]
(remote_op_done) notice: Operation 'reboot'
On Wed, Jul 19, 2023 at 8:33 PM Priyanka Balotra
wrote:
>
> Sure,
> Here are the logs:
>
>
> 63138:Jul 17 14:16:25.132 FILE-2 pacemaker-controld [15962]
> (post_cache_update)debug: Updated cache after membership event 44.
> 63139:Jul 17 14:16:25.132 FILE-2 pacemaker-controld [15962]
>
Sure,
Here are the logs:
63138:Jul 17 14:16:25.132 FILE-2 pacemaker-controld [15962]
(post_cache_update)debug: Updated cache after membership event 44.
63139:Jul 17 14:16:25.132 FILE-2 pacemaker-controld [15962]
(pcmk__set_flags_as) debug: FSA action flags 0x2
On Wed, 2023-07-19 at 23:49 +0530, Priyanka Balotra wrote:
> Hi All,
> I am using SLES 15 SP4. One of the nodes of the cluster is brought
> down and boot up after sometime. Pacemaker service came up first but
> later it faced a fatal shutdown. Due to that crm service is down.
>
> The logs from
Hi All,
I am using SLES 15 SP4. One of the nodes of the cluster is brought down and
boot up after sometime. Pacemaker service came up first but later it faced
a fatal shutdown. Due to that crm service is down.
The logs from /var/log/pacemaker.pacemaker.log are as follows:
Jul 17 14:18:20.093
Thanks Klaus and Ken for your quick support.
Regards,
S Sathish S
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Mon, 2023-06-26 at 08:46 +0200, Klaus Wenninger wrote:
>
>
> On Fri, Jun 23, 2023 at 3:57 PM S Sathish S via Users <
> users@clusterlabs.org> wrote:
> > Hi Team,
> >
> > The pacemaker logs is written in both '/var/log/messages' and
> > '/var/log/pacemaker/pacemaker.log'.
> > Could you
On Fri, Jun 23, 2023 at 3:57 PM S Sathish S via Users
wrote:
> Hi Team,
>
>
>
> The pacemaker logs is written in both '/var/log/messages' and
> '/var/log/pacemaker/pacemaker.log'.
>
> Could you please help us for not write pacemaker processes in
> /var/log/messages? Even corosync configuration
Hi Team,
The pacemaker logs is written in both '/var/log/messages' and
'/var/log/pacemaker/pacemaker.log'.
Could you please help us for not write pacemaker processes in
/var/log/messages? Even corosync configuration we have set to_syslog: no.
Attached the corosync.conf file.
Pacemaker 2.1.6
Hi all,
The final release of Pacemaker 2.1.6 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.6
Highlights include improvements in node attribute management
capabilities, status display, and resource description usage, as well
as a bunch of bug fixes
Hi all,
The second (and possibly final) release candidate for Pacemaker 2.1.6
is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.6-rc2
This release candidate officially deprecates the "moon" attribute of
date_spec elements in rules, and support
Hi all,
The first release candidate for Pacemaker 2.1.6 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.6-rc1
Highlights include new features for managing node attributes, and
easier use of resource descroptions.
Utilization node attributes may now
On Tue, 2023-03-28 at 13:11 +0800, d tbsky wrote:
> Ken Gaillot
> > I'm glad it's resolved, but for future reference, that does
> > indicate a
> > serious problem. It means the fencer is not accepting any requests,
> > so
> > any fencing attempts or even attempts to monitor a fencing device
> >
Ken Gaillot
> I'm glad it's resolved, but for future reference, that does indicate a
> serious problem. It means the fencer is not accepting any requests, so
> any fencing attempts or even attempts to monitor a fencing device from
> that node will fail.
>
That sounds like pacemaker-fenced
On Mon, 2023-03-27 at 14:48 +0800, d tbsky wrote:
> Hi:
>the cluster is running under RHEL 9.0 elements. today I saw log
> report strange errors like below:
>
> Mar 27 13:07:06.287 example.com pacemaker-fenced[2405]
> (qb_sys_mmap_file_open) error: couldn't allocate file
>
Christine caulfield
> It sounds like you're running an old version of libqb, upgrading to
> libqb 2.0.6 (in RHEL 9.1) should fix those messages
Thanks a lot for the quick response! I will arrange the upgrade.
Regards,
tbskyd
___
Manage your
On 27/03/2023 07:48, d tbsky wrote:
Hi:
the cluster is running under RHEL 9.0 elements. today I saw log
report strange errors like below:
Mar 27 13:07:06.287 example.com pacemaker-fenced[2405]
(qb_sys_mmap_file_open) error: couldn't allocate file
Hi:
the cluster is running under RHEL 9.0 elements. today I saw log
report strange errors like below:
Mar 27 13:07:06.287 example.com pacemaker-fenced[2405]
(qb_sys_mmap_file_open) error: couldn't allocate file
/dev/shm/qb-2405-2403-12-A9UUaJ/qb-request-stonith-ng-data:
Interrupted
On Tue, 21 Mar 2023 11:47:23 +0100
Jérôme BECOT wrote:
> Le 21/03/2023 à 11:00, Jehan-Guillaume de Rorthais a écrit :
> > Hi,
> >
> > On Tue, 21 Mar 2023 09:33:04 +0100
> > Jérôme BECOT wrote:
> >
> >> We have several clusters running for different zabbix components. Some
> >> of these
Hi,
On Tue, 21 Mar 2023 09:33:04 +0100
Jérôme BECOT wrote:
> We have several clusters running for different zabbix components. Some
> of these clusters consist of 2 zabbix proxies,where nodes run Mysql,
> Zabbix-proxy server and a VIP, and a corosync-qdevice.
I'm not sure to understand your
On Mon, 2023-03-06 at 16:03 +0300, Alexander Epaneshnikov via Users
wrote:
> Hello. we are using pacemaker 2.1.4-5.el8 and seeing strange errors
> in the
> logs when a request is made to the cluster.
>
> Feb 17 08:18:15 gm-srv-oshv-001.int.cld pacemaker-remoted [2984]
> (handle_new_connection)
On Mon, Mar 6, 2023 at 3:32 PM Christine caulfield
wrote:
> Hi,
>
> The error is coming from libqb - which is what manages the local IPC
> connections between local clients and the server.
>
> I'm the libqb maintainer but I've never seen that error before! Is there
> anything unusual about the
Hi,
The error is coming from libqb - which is what manages the local IPC
connections between local clients and the server.
I'm the libqb maintainer but I've never seen that error before! Is there
anything unusual about the setup on this node? Like filesystems on NFS
or some other networked
Hello. we are using pacemaker 2.1.4-5.el8 and seeing strange errors in the
logs when a request is made to the cluster.
Feb 17 08:18:15 gm-srv-oshv-001.int.cld pacemaker-remoted [2984]
(handle_new_connection) error: Error in connection setup
(/dev/shm/qb-2984-1077673-18-7xR8Y0/qb):
Pacemaker only uses the user and group names directly. It will get the
IDs from the local system, so you can use any IDs you want.
The names themselves are configurable at compile-time. If you're using
pre-built packages, you're stuck with whatever the packager chose (most
likely the defaults,
, Genessi C. Crisolo via Users wrote:
> Dear Clusterlabs team,
>
> Good day!
>
> Would like to know if you can deliver a virtual training for
> Clusterlabs pacemaker administration?
>
> If yes, please share with us the costing and class schedule.
>
> Hope to hear
.
Maybe you can get if from some third party, too.
Regards,
Ulrich
>>> "Genessi C. Crisolo via Users" schrieb am
14.12.2022 um
03:06 in Nachricht
:
> Dear Clusterlabs team,
>
> Good day!
>
> Would like to know if you can deliver a virtual training for Clust
Hi all,
The final release of Pacemaker 2.1.5 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.5
Highlights include support for ACL groups, support for ACL users and
groups with names that aren't unique XML IDs, crm_attribute support for
querying all
Hi all,
The first release candidate for Pacemaker 2.1.5 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.5-rc1
The main highlight is enhancements to the Access Control Lists (ACLs)
feature. ACLs for system groups are now supported, and ACL users
Hi,
If you are using pcs to setup your cluster, then the answer is no. I'm
not sure about crm shell / hawk. Once you have a cluster, you can use
users other than hacluster as Ken pointed out.
Regards,
Tomas
Dne 04. 10. 22 v 16:06 Ken Gaillot napsal(a):
Yes, see ACLs:
Yes, see ACLs:
https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/singlehtml/index.html#document-acls
On Mon, 2022-10-03 at 15:51 +, Jelen, Piotr wrote:
> Dear Clusterlabs team ,
>
> I would like to ask you if there is some possibility to use
> different user (eg.cephhauser)
Dear Clusterlabs team ,
I would like to ask you if there is some possibility to use different user
(eg.cephhauser) for authenticate/setup cluster or there is other method
authenticate/setup cluster, not using password by dedicated pacamker user such
us hacluster ?
Best Regards
Piotr Jelen
On Wed, 2022-06-22 at 17:16 +0530, Priyanka Balotra wrote:
> Hi All,
>
> We are seeing an issue where we performed cluster shutdown followed
> by cluster boot operation. All the nodes joined the cluster excet one
> (the first node). Here are some pacemaker logs around that
> timestamp:
>
>
Hi Klaus,
The config is as follows:
There are 2 nodes in the setup and some resources configured (stonith, IP,
systemd services related).
Sorry, I can share only high level details for this.
- pacemaker version
# rpm -qa pacemaker
pacemaker-2.0.3+20200511.2b248d828-1.10.x86_64
# rpm -qa
On Wed, Jun 22, 2022 at 1:46 PM Priyanka Balotra
wrote:
>
> Hi All,
>
> We are seeing an issue where we performed cluster shutdown followed by
> cluster boot operation. All the nodes joined the cluster excet one (the first
> node). Here are some pacemaker logs around that timestamp:
>
>
Hi All,
We are seeing an issue where we performed cluster shutdown followed by
cluster boot operation. All the nodes joined the cluster excet one (the
first node). Here are some pacemaker logs around that timestamp:
2022-06-19T07:02:08.690213+00:00 FILE-1 pacemaker-fenced[11637]: notice:
Hi all,
The final release of Pacemaker 2.1.4 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.4
This is a bug fix release, fixing regressions in the recent 2.1.3
release.
Many thanks to all contributors of source code to this release,
including Chris
Hi all,
The first (and likely only) release candidate for Pacemaker 2.1.4 is
now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.4-rc1
This is a bug fix release due to a couple of regressions being found in
2.1.3. Since there are very few changes compared
Hi all,
The just-released Pacemaker 2.1.3 had an unfortunate combination of two
unrelated regressions, one in the target-attribute feature for fencing
devices (which allows a fence device to target nodes that have a
specified node attribute set), and one in the test suite for that
feature, which
Hi all,
Pacemaker 2.1.3 has officially been released, with source code
available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.3
Highlights include node health monitoring improvements, improved
monitoring of pacemaker subdaemons, and the ability to show the CIB XML
Hi all,
The second (and possibly last) release candidate for Pacemaker 2.1.3 is
now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.3-rc2
This release candidate adds a few bug fixes. The most noticeable change
is in the RPM packaging: the crm_attribute command
Hi all,
The first release candidate for Pacemaker 2.1.3 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.3-rc1
Highlights previously mentioned on this list include a new cibadmin
option to show the CIB XML colorized according to a given user's ACLs,
a new
With watchdog-only SBD you don't need a fence agent; it's built-in to
Pacemaker when you set the stonith-watchdog-timeout cluster property.
However watchdog-only SBD isn't sufficient for a 2-node cluster,
because each node will assume the other self-fences but neither will.
You need either a
This is my first time using Pacemaker, and I wanted to try watchdog-only
fencing with SBD.
I’m running on Ubuntu 21.10 and Pacemaker v2.0.5
My cluster is up just fine with Dummy services on two nodes.
Systemd says my sbd device is active and running.
But the ‘stonith’ command that Pacemaker uses
On Tue, 2022-03-08 at 10:24 +0200, Viet Nguyen wrote:
> Hi,
>
> May I know is there any API like REST or SOAP or some kind of Java
> libraries to interact with Pacemaker?
>
> I have a Java application and I would like to use that to monitor
> Pacemaker. Like viewing the resource statuses; and
Hi,
May I know is there any API like REST or SOAP or some kind of Java
libraries to interact with Pacemaker?
I have a Java application and I would like to use that to monitor
Pacemaker. Like viewing the resource statuses; and managing resources and
nodes like move resources or stop a node from
Ehy Philip,
sorry for being late, today was a bad day!
to make keycloak reconnect to the postgres db when it fails, you have to
edit your current configuration file (it could be for
example /opt/keycloak/standalone/configuration/standalone-ha.xml or
standalone.xml doublecheck it)
replace the
That would be great!
On Fri, Jan 28, 2022 at 2:50 PM damiano giuliani <
damianogiulian...@gmail.com> wrote:
> Ehy, i solved the issue you talking about few months ago, you have to
> modify .xml configuration on keycloak side, if you re not in hurry monday i
> send you how i fix it.
>
> Damiano
>
Ehy, i solved the issue you talking about few months ago, you have to
modify .xml configuration on keycloak side, if you re not in hurry monday i
send you how i fix it.
Damiano
On Fri, 28 Jan 2022, 20:25 Ken Gaillot, wrote:
> On Fri, 2022-01-28 at 12:15 -0500, Philip Alesio wrote:
> > Hi
On Fri, 2022-01-28 at 12:15 -0500, Philip Alesio wrote:
> Hi Everyone,
>
> I'm attempting to create a failover cluster that uses Postgresql and
> Keycloak and am having difficulty getting Keycloak running. Keycloak
> is using a Postgresql database. In one case I'm using DRBD to
> replicate the
Hi Everyone,
I'm attempting to create a failover cluster that uses Postgresql and
Keycloak and am having difficulty getting Keycloak running. Keycloak is
using a Postgresql database. In one case I'm using DRBD to replicate the
data and in another case I'm using Postgresql. The failure, in both
Hi all,
Pacemaker 2.1.2 has officially been released, with source code
available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.2
Highlights include more flexible syntax in pcmk_host_map and
pcmk_delay_base, and improved log messages and status output for
actions failed
Hi all,
Source code for the second (and likely final) release candidate for
Pacemaker version 2.1.2 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.2-rc2
This just has a few trivial fixes compared to rc1. I will likely
release the final version next week
Source code for the first release candidate for
Pacemaker version 2.1.2 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.2-rc1
This is a fairly small release, so I hope to have maybe one more
release candidate before final release within a month
On 2021-09-09 7:12 p.m., Ken Gaillot
wrote:
Hi all,
Pacemaker 2.1.1 has officially been released, with source code
available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.1
Highlights include a number of regression fixes and other bug
Hi all,
Pacemaker 2.1.1 has officially been released, with source code
available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.1
Highlights include a number of regression fixes and other bug fixes.
For more details, see the ChangeLog in the source repository.
Many
Hi all,
Unless any regressions are found, this will be the last release
candidate before final release of Pacemaker version 2.1.1 in about a
week. It contains a few more minor fixes compared to rc2. Source code
is available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker
On 13.08.2021 22:46, ChittaNagaraj, Raghav wrote:
> Hello Team,
>
> Hope you doing well.
>
> Running into an issue with multi-state resources not running stop function on
> a node but failing over to start the resource on another node part of the
> cluster when corosync process is killed.
>
>
Hello Team,
Hope you doing well.
Running into an issue with multi-state resources not running stop function on a
node but failing over to start the resource on another node part of the cluster
when corosync process is killed.
Note, in the below, actual resource names/hostnames have been
/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.1-rc2
For details, see the ChangeLog in the source repository. Everyone is
encouraged to download, compile and test the new release. We do many
regression tests and simulations, but we can't cover all possible use
cases, so your feedback is important
On Thu, Aug 5, 2021 at 9:25 PM Andrei Borzenkov wrote:
>
> Three nodes A, B, C. Communication between A and B is blocked
> (completely - no packet can come in both direction). A and B can
> communicate with C.
>
> I expected that result will be two partitions - (A, C) and (B, C). To my
>
On 2021-08-05 2:25 p.m., Andrei
Borzenkov wrote:
Three nodes A, B, C. Communication between A and B is blocked
(completely - no packet can come in both direction). A and B can
communicate with C.
I expected that result will be two partitions - (A, C) and (B, C).
Three nodes A, B, C. Communication between A and B is blocked
(completely - no packet can come in both direction). A and B can
communicate with C.
I expected that result will be two partitions - (A, C) and (B, C). To my
surprise, A went offline leaving (B, C) running. It was always the same
node
On Wed, Aug 4, 2021 at 5:30 PM Janusz Jaskiewicz <
janusz.jaskiew...@gmail.com> wrote:
> Hello.
>
> Please forgive the length of this email but I wanted to provide as much
> details as possible.
>
> I'm trying to set up a cluster of two nodes for my service.
> I have a problem with a scenario
Hello.
Please forgive the length of this email but I wanted to provide as much
details as possible.
I'm trying to set up a cluster of two nodes for my service.
I have a problem with a scenario where the network between two nodes gets
broken and they can no longer see each other.
This causes
Hi all,
Source code for the first (and possibly only) release candidate for
Pacemaker version 2.1.1 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.1-rc1
This main goal of this release is to fix a couple of regressions
introduced in 2.1.0 in the command
Hello everyone!!!
Hope you are doing well.
I need some help regarding pacemaker alerts. I have a 36-node cluster setup
with some IP and dummy resources. I have also deployed an alert script for the
cluster that monitors the node and resources and generates alerts on events
occurrence. The alert
On Wed, Jun 9, 2021 at 8:58 PM wrote:
>
> I had generated the docs from a host with older versions of some of the
> doc tools. I regenerated them from a newer host. Some tables still have
> issues, but long lines are now wrapped.
>
Yes, that is fixed, thank you.
> > >
> > > There are problems
rei Borzenkov wrote:
> > On Wed, Jun 9, 2021 at 12:24 AM wrote:
> > >
> > > Hi all,
> > >
> > > Pacemaker 2.1.0 has officially been released, with source code
> > > available at:
> > >
> > >
> > > https://github.com/Clust
On Wed, 2021-06-09 at 12:29 +0300, Andrei Borzenkov wrote:
> On Wed, Jun 9, 2021 at 12:24 AM wrote:
> >
> > Hi all,
> >
> > Pacemaker 2.1.0 has officially been released, with source code
> > available at:
> >
> >
> > https://github.com
On Wed, Jun 9, 2021 at 12:24 AM wrote:
>
> Hi all,
>
> Pacemaker 2.1.0 has officially been released, with source code
> available at:
>
> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.0
>
> Highlights include OCF Resource Agent API 1.1 compatibili
On 2021-06-08 5:24 p.m., kgail...@redhat.com wrote:
> Hi all,
>
> Pacemaker 2.1.0 has officially been released, with source code
> available at:
>
> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.0
>
> Highlights include OCF Resource Age
Hi all,
Pacemaker 2.1.0 has officially been released, with source code
available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.0
Highlights include OCF Resource Agent API 1.1 compatibility,
noncritical resources, and new build-time options. The Pacemaker
documentation
Is there a way to have pacemaker resource groups failover if all floating IP
resources are unavailable?
I want to have multiple floating IPs in a resource group that will only
failover if all IPs cannot work. Each floating IP is on a different subnet and
can be used by the application I
On 01.06.2021 18:20, kgail...@redhat.com wrote:
> On Thu, 2021-05-27 at 20:46 +0300, Andrei Borzenkov wrote:
>> On 27.05.2021 15:36, Nathan Mazarelo wrote:
>>> Is there a way to have pacemaker resource groups failover if all
>>> floating IP resources are unavailable?
>>>
>>> I want to have
Hi all,
Source code for the third (and likely final) release candidate for
Pacemaker version 2.1.0 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.0-rc3
This fixes a couple of minor regressions found in crm_resource and
crm_verify in rc1, and makes a few
On Thu, 2021-05-27 at 20:46 +0300, Andrei Borzenkov wrote:
> On 27.05.2021 15:36, Nathan Mazarelo wrote:
> > Is there a way to have pacemaker resource groups failover if all
> > floating IP resources are unavailable?
> >
> > I want to have multiple floating IPs in a resource group that will
>
On 5/29/21 12:05 AM, Strahil Nikolov wrote:
Most RA scripts are writen in bash.
Usually you can change the shebang to '!#/usr/bin/bash -x' or you can
set trace_ra=1 via 'pcs resource update RESOURCE trace_ra=1
trace_file=/somepath'.
If you don't define trace_file, it should create them in
Most RA scripts are writen in bash.Usually you can change the shebang to
'!#/usr/bin/bash -x' or you can set trace_ra=1 via 'pcs resource update
RESOURCE trace_ra=1 trace_file=/somepath'.
If you don't define trace_file, it should create them in
/var/lib/heartbeat/trace_ra (based on memory -> so
Hello Team,
We have been recently running some tests on our Pacemaker clusters that involve two Pacemaker resources on two nodes respectively. The test case in which we are experiencing intermittent problems is one in which we bring down the Pacemaker resources on both nodes simultaneously. Now
Is there a way to have pacemaker resource groups failover if all floating IP
resources are unavailable?
I want to have multiple floating IPs in a resource group that will only
failover if all IPs cannot work. Each floating IP is on a different subnet and
can be used by the application I
On 27.05.2021 15:36, Nathan Mazarelo wrote:
> Is there a way to have pacemaker resource groups failover if all floating IP
> resources are unavailable?
>
> I want to have multiple floating IPs in a resource group that will only
> failover if all IPs cannot work. Each floating IP is on a
Hi all,
Source code for the second release candidate for Pacemaker version
2.1.0 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.0-rc2
Changes since rc1 include new OCF-related build options discussed in an
earlier message, compatibility with bleeding
Hi all,
Source code for the first release candidate for Pacemaker version 2.1.0
is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.0-rc1
Highlights include support for the OCF Resource Agent API 1.1 standard
(including supporting "Promoted" and &
Hi Sathish,
Sorry, I don't know how to get ruby 2.2.0 for RHEL 7.
The types of support have been explained by Ken. It has already been
said that pcs-0.10 is not supported on RHEL 7.
I would recommend to either downgrade to pacemaker 1.x and pcs-0.9, as
suggested by Ken, or upgrade your
Hi Tomas,
Thanks for your response.
Python 3.6+ package is available in RHEL 7 stream but for ruby 2.2.0+ we don’t
have package available in RHEL 7 stream . how to overcome this problem can you
provide way-forward for the same.
It also stated runtime dependencies of pcs and pcsd.
Thanks and
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
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
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
1 - 100 of 677 matches
Mail list logo
