ure script will automatically determine whether support is
available.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Mon, 2020-03-09 at 11:42 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 06.03.2020 um
> > > > 16:00 in
>
> Nachricht
> :
> > On Fri, 2020‑03‑06 at 08:19 +0100, Ulrich Windl wrote:
> > > > > > Ondrej schrieb am 06.03.2020
&
tor interval=N
meta attributes
rule when ping attribute lt 1 or not defined
enabled=false
The node attribute will be changed only once the ping resource monitor
detects the IP gone, so there will be a window between when the IP
actually disappears and the node attribute is change
F records into DNS for
> clusterlabs.org
> domain.
We definitely should add SPF records. That might help the "not being
delivered" issue, if mail servers are doing a "SPF or DKIM must pass"
test.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
emails sent by the list?
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
failed to validate content
> > >/tmp/ansible.oGK0ye.xml:17: element group: Relax-NG validity error
> > :
> > >Element resources has extra content: group
> > >(main) error: CIB did not pass schema validation
> > >Errors found during check: config not vali
nfsd nfsserver nfs_shared_infodir=/data ;
> \
>pcs resource create nfscfg exportfs
> clientspec="192.168.2.55"
> options=rw,no_subtree_check,no_root_squash directory=/data fsid=0 ; \
>pcs constraint colocation add nfsd with vip ; \
>pcs constraint colocation add nfscfg with nfsd ; \
>pcs constraint order vip then nfsd
Hi all,
The clusterlabs.org server OS upgrade is (mostly) done.
Services are back up, with the exception of some cosmetic issues and
the source code continuous integration testing for ClusterLabs github
projects (ci.kronosnet.org). Those will be dealt with at a more
reasonable time :)
--
Ken
On Fri, 2020-02-28 at 09:37 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 27.02.2020 um
> > > > 23:43 in Nachricht
>
> <43512a11c2ddffbabeee11cf4cb509e4e5dc98ca.ca...@redhat.com>:
>
> [...]
> >
> > > 2. Resources/group
On Thu, 2020-02-27 at 22:39 +0300, Andrei Borzenkov wrote:
> 27.02.2020 20:54, Ken Gaillot пишет:
> > On Thu, 2020-02-27 at 18:43 +0100, Jehan-Guillaume de Rorthais
> > wrote:
> > > > > Speaking about shutdown, what is the status of clean shutdown
> > >
On Thu, 2020-02-27 at 20:42 +0200, Strahil Nikolov wrote:
> On February 27, 2020 7:00:36 PM GMT+02:00, Ken Gaillot <
> kgail...@redhat.com> wrote:
> > On Thu, 2020-02-27 at 17:28 +0100, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Thu, 27 Feb 2020 09:48:
is has been discussed in the
> past.
Ah, that makes sense, I hadn't thought about that. FYI, there is a
stop-all-resources cluster property that would let you disable
everything in one step.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
Hi all,
The ClusterLabs Summit wiki has been updated with a few more photos.
Enjoy ...
http://plan.alteeve.ca/index.php/HA_Cluster_Summit_2020#Photos
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
On Thu, 2020-02-27 at 17:28 +0100, Jehan-Guillaume de Rorthais wrote:
> On Thu, 27 Feb 2020 09:48:23 -0600
> Ken Gaillot wrote:
>
> > On Thu, 2020-02-27 at 15:01 +0100, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Thu, 27 Feb 2020 12:24:46 +01
. will need upgrading.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Thu, 2020-02-27 at 08:12 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 26.02.2020 um
> > > > 16:41 in Nachricht
>
> <2257e2a1e5fd88ae2b915b8241a8e8c9e150b95b.ca...@redhat.com>:
>
> [...]
> > I considered a per-resource and/
e
> > those
> > HA-resources will be down while the node boots." How is that
> > different from
> > not having a HA cluster, or taking those resources temporarily away
> > from the
> > HA cluster? (That was my intitial objection: Why not
there shouldn't be any missed
messages.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Wed, 2020-02-26 at 06:52 +0200, Strahil Nikolov wrote:
> On February 26, 2020 12:30:24 AM GMT+02:00, Ken Gaillot <
> kgail...@redhat.com> wrote:
> > Hi all,
> >
> > We are a couple of months away from starting the release cycle for
> > Pacemaker 2.0.4. I'll
,
> monitor)
>
> Regards,
> Ulrich
Exactly, they typically exist as points other actions can be internally
ordered against.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Wed, 2020-02-26 at 10:33 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 25.02.2020 um
> > > > 23:30 in
>
> Nachricht
> <29058_1582669837_5E55A00B_29058_3341_1_f8e8426d0c2cf098f88fb6330e8a8
> 0586f03043a
> ca...@redhat.com>:
> > H
On Wed, 2020-02-26 at 14:45 +0900, Ondrej wrote:
> Hi Ken,
>
> On 2/26/20 7:30 AM, Ken Gaillot wrote:
> > The use case is a large organization with few cluster experts and
> > many
> > junior system administrators who reboot hosts for OS updates during
> > planned
anually clear a lock with "crm_resource --refresh"
specifying both --node and --resource.
There are some limitations using shutdown locks with Pacemaker Remote
nodes, so I'd avoid that with the upcoming release, though it is
possible.
--
Ken Gaillot
_
ials.
Also, make sure your systemd services are not enabled in systemd itself
(e.g. via systemctl enable). Clustered systemd services should be
managed by the cluster only.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
so you can choose based on whether you want the IP to be functional
only if redis is also functional, or you want the IP to be usable for
other purposes even if redis is down. If redis binds to the specific
IP, then the IP must be first.
--
Ken Gaillot
_
/HA_Cluster_Summit_2020
If anyone wants more in-depth information about the talks, I'm sure the
speakers will be happy to give more details here if asked.
Thanks to everyone involved, including all the speakers and attendees!
--
Ken Gaillot
___
Manage your
On Wed, 2020-01-22 at 08:01 +0200, Strahil Nikolov wrote:
> On January 21, 2020 9:23:35 PM GMT+02:00, Ken Gaillot <
> kgail...@redhat.com> wrote:
> > On Tue, 2020-01-21 at 06:29 +0200, Strahil Nikolov wrote:
> > > On January 20, 2020 5:57:18 PM GMT+02:00, Ken Gaillot
On Tue, 2020-01-21 at 06:29 +0200, Strahil Nikolov wrote:
> On January 20, 2020 5:57:18 PM GMT+02:00, Ken Gaillot <
> kgail...@redhat.com> wrote:
> > On Sat, 2020-01-18 at 20:54 +, Strahil Nikolov wrote:
> > > Hello Community,
> > >
> > >
> >
t;
> Do I need to add some other settings to the fence_rhevm stonith agent
> ?
>
>
> Manually running the status command from drbd2/drbd3 is OK:
>
>
> [root@drbd3 ~]# fence_rhevm -o status --ssl --ssl-secure -a
> engine.localdomain --username='fencerdrbd@internal'
reason; it probably goes back to when the feature was
experimental. Feel free to file a bug with Red Hat asking for it to be
enabled.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
gt; Let us know if any additional information required from our end.
>
> Regards,
> S Sathish S
See /etc/sysconfig/pacemaker or the equivalent on your OS (/etc/default
or wherever). You can set PCMK_logfacility=none, or raise
PCMK_logpriority to see only the most important messages
rticipate in DC
> election etc. Could someone guide me on an recommended approach to do
> this ?
>
> Thanks!
> Prasad.
Pacemaker Remote would be perfect for that:
https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/Pacemaker_Rem
r: pacemaker-
> controld[7517] exited with status 1 (Error occurred)
> Dec 30 10:02:37 vmc0621 pacemakerd[3048]: notice: Respawning failed
> child process: pacemaker-controld
>
> Please let us know if any further logs required from our end.
>
> Thanks and Regards,
> S Sathish S
> __
and can be considered deprecated since CLUSTERIP itself is
deprecated. A pull request with an xt_cluster implementation would be
very welcome, as it's a low priority for available developers.
> Thanks a lot!
>
>
> Att,
>
> Marcus Vinícius
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
r: region-ctrl-1
> nodeid: 1
> }
> }
I know you've tried various things with the config, so I'm not sure
what happened when, but with only those two nodes listed explicitly and
multicast configured, it does make sense that the local node (which
isn't listed) would join with a
known
> as region-ctrl-2
> cib: info: qb_ipcs_us_publish:server name: cib_ro
> cib: info: qb_ipcs_us_publish:server name: cib_rw
> cib: info: qb_ipcs_us_publish:server name: cib_shm
> cib: info: pcmk_cpg_membership: Node 1084777441
> joined group cib (counter=0.0, pid=0, unchecked for rivals)
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
>
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
additional maybe who already
contacted me.
If you're thinking of going and aren't on that list, please let me know
as soon as possible.
I should have hotel details soon.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman
privately so we can firm up the head count and
finalize planning.
Thanks,
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
Linux kernel since 2015. IPaddr2 cloning
therefore must be considered deprecated as well. (Using it for a single
floating IP is still fully supported.)
IPaddr2 could be modified to use a newer iptables capability called
"xt_cluster", but someone would ha
) has been fixed when both a
> > guest node or bundle and the host running it needs to be fenced,
> > but
> > can't (due to quorum loss, for example).
> >
> > For more details about changes in this release, see:
> >
> > https://github.com/ClusterLabs/pace
uot;warning",
"error", or "critical" level.
I could see an argument for lowering the "calculated"/"complete"
messages to "info" level (which doesn't go into the system log) when no
actions are needed. The state transition messages should stay
oned above would apply to all nodes that meet
the condition.
> Obviously such things have to be done using rules, but I haven't
> found any examples going in such direction.
>
> Regards,
> Ulrich
--
Ken Gaillot
___
Manage your subscription:
htt
s/pacemaker/blob/2.0/ChangeLog
Many thanks to all contributors of source code to this release,
including Aleksei Burlakov, Chris Lumens, Gao,Yan, Hideo Yamauchi, Jan
Pokorný, John Eckersberg, Kazunori INOUE, Ken Gaillot, Klaus Wenninger,
Konstantin Kharlamov, Munenari, Roger Zhou, S. Schu
emote/
The scalability of Pacemaker Remote isn't well known. Some users have
reported problems with as few as 40 remote nodes, while others have
gotten above 100 without problems.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterla
> If there is not enough time, we can shrink them into one slot.
I'm planning on 1 hour per talk on average (about 40-45 minutes
speaking plus 10-15 minutes Q and a few minutes between talks). If
you'd prefer more or less let me know, but you can plan on that.
>
> On 15/10/2019 23:42, Ken
On Fri, 2019-11-15 at 14:35 +0100, Jehan-Guillaume de Rorthais wrote:
> On Thu, 14 Nov 2019 11:09:57 -0600
> Ken Gaillot wrote:
>
> > On Thu, 2019-11-14 at 15:22 +0100, Ulrich Windl wrote:
> > > > > > Jehan-Guillaume de Rorthais schrieb am
> > >
Q
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with
> number 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
> PO6 3AU
--
Ken Gaillot
___
Manage your subscript
On Thu, 2019-11-14 at 15:22 +0100, Ulrich Windl wrote:
> > > > Jehan-Guillaume de Rorthais schrieb am
> > > > 14.11.2019 um
>
> 15:17 in
> Nachricht <20191114151719.6cbf4e38@firost>:
> > On Wed, 13 Nov 2019 17:30:31 ‑0600
> > Ken Gail
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
contain the exit reason if one was provided by
the resource agent, for easier troubleshooting.
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 an
On Thu, 2019-11-07 at 10:16 +0100, wf...@niif.hu wrote:
> Ken Gaillot writes:
>
> > I edited it so that the default and description are combined:
> >
> > How to determine which machines are controlled by the device.
> > Allowed
> > values:
> >
>
On Thu, 2019-11-07 at 07:43 +, Roger Zhou wrote:
>
> On 11/7/19 1:55 AM, Andrei Borzenkov wrote:
> > 06.11.2019 18:55, Ken Gaillot пишет:
> > > On Wed, 2019-11-06 at 08:04 +0100, Ulrich Windl wrote:
> > > > > > > Ken Gaillot schrieb am 05.11
n dc-dcb-corosync-
> haproxy-09: 0
> group_color: HAProxy_43234 allocation score on dc-dcb-corosync-
> haproxy-07: 0
> group_color: HAProxy_43234 allocation score on dc-dcb-corosync-
> haproxy-08: 0
> group_color: HAProxy_43234 allocation score on dc-dcb-corosync-
> hap
On Wed, 2019-11-06 at 08:06 +0100, Michele Baldessari wrote:
> On Tue, Nov 05, 2019 at 02:21:29PM -0300, Rafael David Tinoco wrote:
> > On 04/11/2019 23:07, Ken Gaillot wrote:
> > > Hi all,
> > >
> > > A reminder: We are still interested in ideas for talks, an
On Wed, 2019-11-06 at 08:04 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 05.11.2019 um
> > > > 16:05 in
>
> Nachricht
> :
> > Coincidentally, the documentation for the pcmk_host_check default
> > was
> > recently updat
considering the possibilities.
On Wed, 2019-11-06 at 08:22 +0100, Ulrich Windl wrote:
> > > > Valentin Vidic schrieb am
> > > > 05.11.2019 um
>
> 20:35
> in Nachricht <20191105193555.gg27...@valentin-vidic.from.hr>:
> > On Mon, Nov 04, 2019 at 08:07:51PM ‑
On Tue, 2019-11-05 at 14:21 -0300, Rafael David Tinoco wrote:
> On 04/11/2019 23:07, Ken Gaillot wrote:
> > Hi all,
> >
> > A reminder: We are still interested in ideas for talks, and rough
> > estimates of potential attendees. "Maybe" is perfectly fine at thi
On Tue, 2019-11-05 at 00:39 -0500, Digimer wrote:
> On 2019-11-04 9:07 p.m., Ken Gaillot wrote:
> > Hi all,
> >
> > A reminder: We are still interested in ideas for talks, and rough
> > estimates of potential attendees. "Maybe" is perfectly fine at this
>
> > > buster).
>
> That's why I asked:
>
> > > Ram, what happens if you set pcmk_host_check to static-list?
>
> Of course the developers are most welcome to chime in with their
> intentions and changes concerning this, I haven't got the time to dig
> into the core right now. Tough I'm very much interested for my own
> sake
> as well, because I'm about to bring up a buster cluster with very
> similar config.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
Hi all,
A reminder: We are still interested in ideas for talks, and rough
estimates of potential attendees. "Maybe" is perfectly fine at this
stage. It will let us negotiate hotel rates and firm up the location
details.
On Tue, 2019-10-15 at 16:42 -0500, Ken Gaillot wrote:
&
t we can't cover all
possible use cases, so your feedback is important and appreciated.
A 1.1.22-rc2 version with selected backports from this release will
also be released soon.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.o
> origin=notify_crmd
> Oct 30 12:22:37 duke pacemaker-based [1698]
> (cib_process_ping) info: Reporting our current digest to duke:
> 2eb5c8ee7e7df17c5737befc7d93de76 for 0.37.6 (0x55a5ab900f70 0)
>
> ###
>
> Here is my corosync config for your reference,
>
; 2.35.0 of the CIB to disk (digest:
> > 8e3625f4ef74b6fe6c6429757023b7e9)
> >
> > I mean: I know that SBD will use the watchdog for fencing if
> > everything else fails, but why is this message logged so many
> > times?
> >
>
> This message is also misleading. Pacem
"? ;-))
> So my argument for "status" simply is that the data describes the
> status.
The idea is that if the output is saved to a file, someone looking at
that file later could easily figure out where it came from, even
without any other context.
> > All of the format o
luding Aleksei Burlakov, Chris Lumens, Gao,Yan, Hideo Yamauchi, Jan
Pokorný, John Eckersberg, Kazunori INOUE, Ken Gaillot, Klaus Wenninger,
Konstantin Kharlamov, Munenari, Roger Zhou, S. Schuberth, Tomas
Jelinek, and Yuusuke Iida.
1.1.22-rc1, with selected backports from this release, will also be
Linux context than systemd, so
> > policies might not be set up correctly.
> > --
> > Ken Gaillot
>
> Alas, SELinux is not in use.
>
>
> I am thinking that the apache OCF module is not starting up apache
> with the modules that it needs.
>
> Again, s
TY 100 and 200 respectively.
> >
> > Just to make the whole thing more confusing: I noticed that
> > SRVRDSW03,
> > that is (implicitly) not allowed to get the ClusterIP resource is
> > marked
> > (correctly) as -INFINITY from crm_simulate. So the opt in
&g
forth.
I'm excited about the chance for developers and users to meet in
person. Past summits have been helpful for shaping the direction of the
projects and strengthening the community. I look forward to seeing many
of you there!
--
Ken Gaillot
iled,
and likely keep trying to restart it fruitlessly)
- Convenience of things like putting a node in standby mode, and
checking resource status on all nodes with one command
If you do move them to systemd, be sure to use the resource-agents-deps
target to ensure they're started before pacemak
On Tue, 2019-10-15 at 08:42 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 15.10.2019 um
> > > > 00:47 in
>
> Nachricht
> :
> > Hi all,
> >
> > With Pacemaker 2.0.2, we introduced a new experimental option for
> > XML
> &
=/path/to/copied/cib.xml
crm_mon . That won't work with curses output, but you can test
text, HTML, and XML that way.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https
t; cluster will finish cleanup and start on the new node. 'crm
> resource cleanup ncoa_apache' hangs, as well.
>
> Apache starts up just fine from the systemctl command, so it's not
> the Apache config that's broken.
>
> Suggestions?
>
> John Reynolds SMUnix
If
directory). That will
remain the default behavior, but the new option "make RPMDEST=subtree
rpm" will put the RPM sources in the top-level build directory and
everything else in a dedicated "rpm" subdirectory of the build tree.
This kee
h the throttle ?
Those messages could definitely be improved. The particular mode values
indicate no significant CPU load (), low load (0001), medium
(0010), high (0100), or extreme (1000).
I wouldn't expect a CPU spike to lock up corosync for very long, but it
could be related somehow.
>
> Thanks.
>
>
> Bernd
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
ve a two node cluster on SLES 12 SP4, with pacemaker-
> 1.1.19+20181105.ccd6b5b10-3.13.1.x86_64 and corosync-2.3.6-
> 9.13.1.x86_64.
>
> Bernd
I believe it would work to unmanage the other resources, change the
configuration, wait for the changed resource to restart, then re-
On Wed, 2019-10-09 at 20:10 +0200, Kadlecsik József wrote:
> On Wed, 9 Oct 2019, Ken Gaillot wrote:
>
> > > One of the nodes has got a failure ("watchdog: BUG: soft lockup
> > > -
> > > CPU#7 stuck for 23s"), which resulted that the node could
-
> E-mail : kadlecsik.joz...@wigner.mta.hu
> PGP key: http://www.kfki.hu/~kadlec/pgp_public_key.txt
> Address: Wigner Research Centre for Physics
> H-1525 Budapest 114, POB. 49, Hungary
> ___
> Man
Pokorný wrote:
> Neither bugs.c.o nor lists.c.o work for me ATM.
> Either it resolves by itself, or Ken will intervene, I believe.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home:
was better
supported on RHEL 6.
At least with corosync 2, I believe it is possible to configure IP
addresses as node names when setting up the cluster, but I'm not sure
there's a good reason to do so. "update-origin" is just a comment
indicating which node made the most recent
nd through this list’s archive; haven’t found my
> answer. I’m missing something in corosync, apache, or systemd.
> Please advise.
>
>
> John Reynolds, Contractor
> San Mateo Unix
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
>
> > > primitive IPSHARED IPaddr2 \
> > > params ip=10.10.10.5 nic=eth0 cidr_netmask=24 \
> > > meta migration-threshold=2 failure-timeout=900 target-
> > role=Started \
> > > op monitor interval=20 timeo
UE pairs and set them as environment
variables.
This allows you to set not only PCMK_remote_address, but other
Pacemaker environment variables such as PCMK_debug, to a different
value for the container to use on each host.
The first release candidate is expected in a couple of weeks.
--
Ken Gail
e?
> >
> > f you have faced this issue/have knowledge, please let us know.
> >
> > Thanks.
>
>
> Hello,
>
> I didn't receive any reply on this issue.wondering whether there are
> no opinions or whether pacemaker with pgsql is not recommended?.
>
>
> Thanks!
Hi,
There are quite a few pacemaker+pgsql users active on this list, but
they may not have time to respond at the moment. Most are using the PAF
agent rather than the pgsql agent (see
https://github.com/ClusterLabs/PAF ).
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
date_spec.
Pacemaker will continue to check at least as often as cluster-recheck-
interval, both to evaluate date_spec entries and as a fail-safe in case
of certain types of scheduler bugs.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clust
tion=status\nPARAMETER=VALUE\nPARAMETER=VALUE\n..." | /path/to/agent
where PARAMETER=VALUE entries are what you have configured in the
cluster. If the problem isn't obvious from that, you can try adding a
debug_file parameter.
--
Ken Gaillot
__
gt; I attached the log of the transition.
>
> Regards,
> Dennis
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
c will "pet" from its main loop. From corosync.conf(5):
>
> > In a cluster with properly configured power fencing a watchdog
> > provides no additional value. On the other hand, slow watchdog
> > communication may incur multi-s
ster status) are triggered by
changes in the CIB. last-lrm-refresh isn't really special in any way,
it's just a value that can be changed arbitrarily to trigger a new
transition when nothing "real" is changing.
I'm not sure what would actually be setting it these days; its use has
rLabs/OCF-spec
The ra/next directory is where we're putting proposed changes (ra-
api.rng is the RNG). Once accepted for the upcoming 1.1 standard, the
changes are copied to the ra/1.1 directory, and at some point, 1.1 will
be officially adopted as the current standard.
So, pull request
On Thu, 2019-09-05 at 07:57 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 04.09.2019 um
> > > > 16:26 in
>
> Nachricht
> <2634f19382b90736bdfb80b9c84997111479d337.ca...@redhat.com>:
> > On Wed, 2019‑09‑04 at 10:07 +0200, Jehan‑Guillaum
On Wed, 2019-09-04 at 10:07 +0200, Jehan-Guillaume de Rorthais wrote:
> On Tue, 03 Sep 2019 09:35:39 -0500
> Ken Gaillot wrote:
>
> > On Mon, 2019-09-02 at 15:23 +0200, Ulrich Windl wrote:
> > > Hi!
> > >
> > > Are there any recommendations where to pla
On Wed, 2019-09-04 at 10:09 +0200, Jehan-Guillaume de Rorthais wrote:
> On Wed, 04 Sep 2019 07:54:50 +0200
> "Ulrich Windl" wrote:
>
> > > > > Ken Gaillot schrieb am 03.09.2019 um
> > > > > 16:35 in
> >
> > Nachricht
&
to follow the FHS, you might consider /usr/share if you're
installing via custom packages, /usr/local/share if you're just
installing locally, or /srv in either case.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
wonder whether this will be the default status reporting
> going forward (I will try the 2.0 branch soon).
It indeed was changed in the 2.0.0 release. RHEL 7 backported the
change from there.
>
> Thanks,
> Chris
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
deid 739512331
> crmd: notice: get_node_name: Could not obtain a node name for
> corosync nodeid 739512331
> crmd: info: pcmk_cpg_membership: Node 739512331 still member
> of group crmd (peer=(null):7281, counter=0.0, at least once)
> crmd: info: crm_update_peer_p
g one of pe-*-series-max cluster options misconfigured.)
>
> > The message was written after an announced resource move to the new
> > node.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
get better integrations
> with RHEL 7, CentOS 7, an edge release of Ubuntu, or some other
> distribution?
There are advantages and disadvantages to changing either of the above,
but I doubt any choice will be easier, just a different set of
roadblocks to work through.
> Thank y
y negative preference to a node
where a single attribute is 0 (one rule for each attribute).
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
dheit und Umwelt (GmbH)
> Ingolstaedter Landstr. 1
> 85764 Neuherberg
> www.helmholtz-muenchen.de
> Aufsichtsratsvorsitzende: MinDir'in Prof. Dr. Veronika von Messling
> Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep,
> Heinrich Bassler, Kerstin Guenther
> R
0:0;68:6583:0:d941efc1-de73-4ee4-b593-
> > > f65be9e90726"
> > > exit-reason="" on_node="h11" call-id="800" rc-code="0" op-
> > > status="0"
> > > i
501 - 600 of 1689 matches
Mail list logo
