On Tue, 2018-08-21 at 07:49 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 20.08.2018 um
> > > > 16:49 in
>
> Nachricht
> <1534776566.6465.5.ca...@redhat.com>:
> > On Mon, 2018‑08‑20 at 10:51 +0200, Ulrich Windl wrote:
> > >
ing "-G" to see the current scores or
"-v " to change them. The node with the highest score will be
promoted.
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
had
> written a monitor for HP-UX' cluster that did not have this problem,
> even though the configuration files were read from NFS (It's not
> magic: Just periodically copy them to shared memory, and read the
> config from shared memory).
>
> Regards,
> Ulrich
--
Ken
7:26Z"
>
> One problem is that the date value is not a constant, and it had to
> be compared against the current date
>
> Regards,
> Ulrich
crm_resource --clear -r RSC will clear all cli-* constraints
--
Ken Gaillot
___
U
t; The node is not completely up-to-date, and it's using pacemaker-
> 1.1.12-18.1...
>
> Regards,
> Ulrich
>
>
> _______
> Users mailing list: Users@clusterlabs.org
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> Proj
t; Here you have some of my configuration settings on node 1
> > > > > > > (I probed
> > > > > > > already
> > > > > > > to change rrp_mode):
> > > > > > >
> > > > > > > *- corosync.conf*
> > > > > > >
> > > > > > >
> > >
}
> }
> service {
> name: pacemaker
> ver: 1
> }
> amf {
> mode: disabled
> }
>
> Thanks in advance for the help.
> Prasad
>
> ___
> Users mailing list: Users@clusterlabs.org
> https://lists.clusterlabs.
g a
> very
> short interval sequentially (i.e. no intermittent failure recovered
> with
> a restart of lrmd, AFAICT). In case it can have any bearing, how do
> you start pacemaker -- systemd, initscript, as a corosync plugin,
> something else?
--
Ken Gaillot
device utilization, then look for
> network bottlenecks...
>
> A new corosync release cannot fix those, most likely.
>
> Regards,
> Ulrich
>
> >
> > In any case, for the current scenario, we did not see any
> > scheduling
> > related messages.
> >
&
to leave
this as a known issue, and rely on the workarounds.
On Mon, 2018-07-16 at 09:21 -0500, Ken Gaillot wrote:
> Hi all,
>
> The just-released Pacemaker 2.0.0 and 1.1.19 releases have an issue
> when a Pacemaker Remote node is upgraded before the cluster nodes.
>
> Pacemaker 2.0.0 contain
mailing list: Users@clusterlabs.org
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.
> pdf
> Bugs: http://bugs.clusterlabs.org
--
Ken Gaillot
rading
any Pacemaker Remote nodes (which is the recommended practice anyway).
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting sta
mailing list: Users@clusterlabs.org
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.
> pdf
> Bugs: http://bugs.clusterlabs.org
--
Ken Gaillot
rue
> >
> > Quorum:
> > Options:
> >
> >
> >
> > ___
> > Users mailing list: Users@clusterlabs.org
> > https://lists.clusterlabs.org/mailman/listinfo/users
> >
> > Project Home: http://www.clusterlabs.o
On Thu, 2018-08-30 at 08:28 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 29.08.2018 um
> > > > 20:30 in
>
> Nachricht
> <1535567455.5594.5.ca...@redhat.com>:
> > On Wed, 2018‑08‑29 at 13:30 +0200, Ulrich Windl wrote:
> > > Hi!
&
uot; resource has scores 0, 1, and -INFINITY, and the
> ":1" resource has score 1 once and -INFINITY twice.
>
> When I look at the "clone_solor" scores, the prm_DLM:* primitives
> look as expected (no -INFINITY). However the cln_DLM clones have
> score like 1,
\
> default-resource-stickiness=200 \
> stonith-timeout=180s \
> last-lrm-refresh=1534489943
>
>
> Thanks
>
> César Hernández Bañó
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
htt
the cluster itself) or some external program.
If it's the cluster, I'd look at the "pengine:" logs on the DC before
that, to see if there are any hints (node unclean, etc.). Then keep
going backward until the ultimate cause is found.
--
Ken Gaillot
; Filesystem(p_fs_datosweb)[962]: 2018/08/31_11:00:05 INFO: Running
> start for /dev/drbd/by-res/datoswebstorage on /mnt/datosweb
> Filesystem(p_fs_database)[961]: 2018/08/31_11:00:05 INFO: Running
> start for /dev/drbd/by-res/databasestorage on /mnt/database
>
>
> ..
>
>
> Can
t; Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratc
> > h.pdf
> > Bugs: http://bugs.clusterlabs.org
>
>
>
> ___________
> Users mailing list: Users@clusterlabs.org
> https://lists.clusterlabs.org/mailman/listinfo/
On Wed, 2018-09-05 at 09:32 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 04.09.2018 um
> > > > 19:21 in Nachricht
>
> <1536081690.4387.6.ca...@redhat.com>:
> > On Tue, 2018-09-04 at 11:22 +0200, Ulrich Windl wrote:
> > >
t;
>
> Oh :( I'm using Pacemaker-1.1.14.
> Do you know if this reboot retries are just run 3 times? All the
> tests I've done the rebooting is finished after 3 times.
>
> Thanks
> Cesar
No, if I remember correctly, it would just keep going until
On Wed, 2018-09-05 at 09:51 -0500, Ken Gaillot wrote:
> On Wed, 2018-09-05 at 16:38 +0200, Cesar Hernandez wrote:
> > Hi
> >
> > >
> > > Ah, this rings a bell. Despite having fenced the node, the
> > > cluster
> > > still conside
rom source, you can apply the patch that fixes the issue
to the 1.1.14 code base:
https://github.com/ClusterLabs/pacemaker/commit/98457d1635db1222f93599b6021e662e766ce62d
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
https://list
onfigure primitive RADIUS-IP ocf:heartbeat:IPaddr2 \
> params ip="192.168.0.9" nic="eth0" cidr_netmask="24" \
> op monitor interval=10s timeout=20s
> crm configure primitive RADIUS lsb:freeradius op monitor interval=10s
> timeout=20s
> crm configure clone RADI
ifference, whether the resource cannot run on an online
> node, or is unable due to a standby or offline node?
>
> Regards,
> Ulrich
Interleave=false only applies to instances that will be started in the
current transition, so offline nodes don't prevent dependent resources
from sta
6-12.el7.x86_64)
>
> /Ian
This sounds like a bug. Feel free to submit a report at
bugs.clusterlabs.org and attach the policy engine input file with the
unexpected behavior.
FYI a group's stickiness is the sum of the stickiness of each active
member, though no score can be bigger than I
to handle large time jumps. Jumps
forward aren't too bad, but jumps backward can cause significant
trouble.
> # pacemakerd --version
> Pacemaker 1.1.16
> Written by Andrew Beekhof
> # corosync -v
> Corosync Cluster Engine, version '2.4.2'
> Copyright (c) 2006-2009 R
ieve the
note about the version shipped with CentOS 7.1 is no longer an issue
with recent versions.
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterl
; if I have a resource threshold set >1, i get start->monitor->stop
> > cycle
> > until the threshold is consumed
>
> Then either your start is broken, or your monitor is broken. Try to
> validate your RA using ocf-tester before using it.
>
> Regards,
&g
ason not to do this is that if you use 0,
> > > > > > > then don't use
> > > > > > > anything at all (0 is default), and any other value
> > > > > > > causes avoidable
> > > > > > > fence delays.
> > > &
> > >
> > > Project Home: http://www.clusterlabs.org
> > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scra
> > > tch.pdf
> > > Bugs: http://bugs.clusterlabs.org
> > >
> >
> > ___
> > Users m
nks to all contributors of source code to this release,
including Andrew Beekhof, Gao,Yan, Hideo Yamauchi, Jan Pokorný, Ken
Gaillot, and Klaus Wenninger.
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailma
ation must be done first. So
maybe the idea was to always require someone to specify run levels. But
it does make more sense that they would be listed in the LSB header.
One reason it wouldn't have been an issue before is some older distros
use the init script's chkconfig header ins
could even combine everything into a single custom resource agent
for use as a master/slave resource, where the master is the only
instance that actually runs the resource, and the slaves just act on
the notifications.
>
> Regards,
> Klaus
>
> > Thanks
> >
> > /Ian.
er Explained" document has grown large enough that topics
related to cluster administration have been moved to their own new
document, "Pacemaker Administration":
http://clusterlabs.org/pacemaker/doc/
Many thanks to all contributors of source code to this release,
including Andrew Beekho
> > Also, is there a way to clear one specific item from the list, or
> > is clearing
> > all the only option?
>
> pcs failcount reset [node]
With the low level tools, you can use -r / --resource and/or -N / --
node with crm_resource to limit the clean-up.
--
_
> Users mailing list: Users@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.
> pdf
> Bugs: http://bugs.clusterlabs.org
--
report.
> The question is: is there a sane way to run VMs under pacemaker's
> control? If yes, is it described somewhere?
>
>
> --
> Pavel
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.
nt for data integrity.
Native replication would avoid all that.
> 2018-03-07 10:20 GMT+01:00 Klaus Wenninger <kwenn...@redhat.com>:
> > On 03/07/2018 10:03 AM, Mevo Govo wrote:
> > > Thanks for advices, I will try!
> > > lados.
> > >
> >
r 9 10:10:21 rh74-test pacemakerd[17719]: notice: Respawning
> failed child process: pengine
> Mar 9 10:10:21 rh74-test pacemakerd[17719]: info: Using uid=990
> and group=984 for process pengine
> Mar 9 10:10:21 rh74-test pacemakerd[17719]: info: Forked child
> 1
into corosync :)
> > > >
> > > > > Regards,
> > > > > Honza
> > > > >
> > > > > >
> > > > > > help would be appreciated, much thanks!
> > > > > >
> > > > > > cheers,
> > > > > > Thomas
> &g
We do many regression tests and simulations, but we can't cover all
possible use cases, so your feedback is important and appreciated.
Many thanks to all contributors of source code to this release,
including Andrew Beekhof, Gao,Yan, Hideo Yamauchi, Jan Pokorný, and Ken
Gaillot. Thanks also to Fabio DiNitt
er the convenient 15-character limit anyway.
On Wed, 2018-03-28 at 12:40 -0500, Ken Gaillot wrote:
> Hi all,
>
> Andrew Beekhof brought up a potential change to help with reading
> Pacemaker logs.
>
> Currently, pacemaker daemon names are not intuitive, making it
> difficult to
On Tue, 2018-04-10 at 08:50 +0200, Jehan-Guillaume de Rorthais wrote:
> On Tue, 10 Apr 2018 00:54:01 +0200
> Jan Pokorný <jpoko...@redhat.com> wrote:
>
> > On 09/04/18 12:10 -0500, Ken Gaillot wrote:
> > > Based on the list discussion and feedback I cou
e_state[@uname='xxx-a']/transient_attributes: OK (rc=0,
> origin=xxx-b/crmd/88, version=0.164.37)
>
> This the repeats forevermore ...
>
> Thanks for any hints,
>
> cheers,
>
> Stefan
--
Ken Gaillot <kgail...@redhat.com>
_
On Wed, 2018-04-11 at 08:49 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot <kgail...@redhat.com> schrieb am 09.04.2018 um
> > > > 19:10 in Nachricht
>
> <1523293841.5734.7.ca...@redhat.com>:
> > Based on the list discussion and feedback I
l-ha pgsqld notify=true
> interleave=true;
>
>
> Sometimes it reports the following error, how to configure to avoid
> it?
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.o
ce/VIP stuff does, but you probably want
to write your own OCF resource agent (see IPaddr2 as an example) to
manage the IP, and let Pacemaker call it as needed.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs
On Tue, 2018-04-10 at 00:02 +0200, Jehan-Guillaume de Rorthais wrote:
> On Tue, 03 Apr 2018 17:35:43 -0500
> Ken Gaillot <kgail...@redhat.com> wrote:
>
> > On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote:
> > > On 04/03/2018 05:43 PM, Ken Gaillot wrote:
&g
it.
What log messages do you see from corosync and pacemaker indicating
that the node is down? Do you have fencing configured and tested?
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clus
onf doesn't exist',
> last-rc-change='Fri Apr 6 13:16:39 2018', queued=0ms, exec=0ms
> ==
>
> We regard this behavior as a problem.
> Is there a way to avoid this behavior?
>
> Regards, Yusuke
Hi Yusuke,
One possibility would be to implement network fabric fencing a
; > minutes after the cluster starts.
> >
> > Why is there about 15 minutes delay every time?
>
> This was a bug in Pacemaker up to 1.1.17. I did a report about this
> last August and Ken Gaillot fixed it few days later in 1.1.18. See:
>
> https://lists.clusterlabs.or
t; useful
> > to check a basic sanity of the custom agents:
> > https://github.com/ClusterLabs/resource-agents/tree/master/tools/oc
> ft
>
>
> I did run ocf-tester and the result was passed. Here I carefully read
> the log. When this error was printed in the log, the late
best way is via a github pull request at:
https://github.com/ClusterLabs/pcs
If you are not familiar with github, or can't go that route for
whatever reason, let us know.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterla
y to automatically calculate just a portion of the
score.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started
,
And show the world your uptime.
Keep serving all the things you can.
Standby your node.
Users list members will vote on all submissions, and the winner will
receive a COMPLETE SET of all available ClusterLabs swag!*
--
Ken Gaillot <kgail...@redhat.com>
* DISCLAIMERS: ClusterLabs current
d, PREFIX-state
crmd: PREFIX-controld, PREFIX-clusterd, PREFIX-controller
lrmd: PREFIX-locald, PREFIX-resourced, PREFIX-runner
pengine: PREFIX-policyd, PREFIX-scheduler
stonithd: PREFIX-fenced, PREFIX-stonithd, PREFIX-executioner
pacemaker_remoted: PREFIX-remoted, PREFIX-remote
--
will be *probed* on every node (a one-time monitor
action to check whether they are already running there), but they
should only be *started* on allowed nodes.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
http
> be active on the same node. It means that in your case of
> >
> > > id="pcs_rsc_colocation_set_drbdfs_set_drbd.master_inside-interface-
> > sameip.master_outside-interface-sameip.master"
> > score="INFINITY">
> >
> >
&
(c1+c6). Before
starting the db, you want a resource that checks whether the original
config needs repair, and if so, copy it from the backup outside DRBD.
It sounds like you should make a copy of the oracle agent, and modify
its start action to do what you want.
> 2018-03-08 20:12 GMT+01:00 Ken Gaill
raid that this could be the cause of my resources falling back
> to a node that has recovered from a fail over although I have a
> stickiness score of INFINITY.
>
> Thanks,
> George
> ___
> Users mailing list: Users@clusterlabs.org
>
> My questions are:
> > >
> > > 1. is it possible to cancel the fencing request
> > > 2. is it possible reset the node status to "online" ?
> >
> > Not that I'm aware of.
>
> Argh!
>
> ++
You could fix the problem with the sto
e.
> --
> Sam Gardner
> Trustwave | SMART SECURITY ON DEMAND
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clu
On Tue, 2018-04-03 at 07:36 +0200, Klaus Wenninger wrote:
> On 04/02/2018 04:02 PM, Ken Gaillot wrote:
> > On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Sun, 1 Apr 2018 09:01:15 +0300
> > > Andrei Borzenkov <arvidj...@gmail.c
On Tue, 2018-04-03 at 08:33 +0200, Kristoffer Grönlund wrote:
> Ken Gaillot <kgail...@redhat.com> writes:
>
> > > I
> > > would vote against PREFIX-configd as compared to other cluster
> > > software,
> > > I would expect that daem
mplify things but
> perhaps not.
Groups are easier to follow if you have simple colocation+order
sequences.
Sets can help with more complicated set-ups, but they are tricky to get
right and always difficult to read.
--
Ken Gaillot <kgail...@redhat.com>
On Tue, 2018-04-03 at 21:33 +0200, Jehan-Guillaume de Rorthais wrote:
> On Mon, 02 Apr 2018 09:02:24 -0500
> Ken Gaillot <kgail...@redhat.com> wrote:
> > On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Sun, 1 Apr 2018 09:01:15 +03
On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote:
> On 04/03/2018 05:43 PM, Ken Gaillot wrote:
> > On Tue, 2018-04-03 at 07:36 +0200, Klaus Wenninger wrote:
> > > On 04/02/2018 04:02 PM, Ken Gaillot wrote:
> > > > On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guill
On Thu, 2018-03-29 at 10:35 +0200, Kristoffer Grönlund wrote:
> Ken Gaillot <kgail...@redhat.com> writes:
>
> > Hi all,
> >
> > Andrew Beekhof brought up a potential change to help with reading
> > Pacemaker logs.
> >
> > Currently,
vinash Sharma
>
> On Fri, Feb 23, 2018 at 8:57 PM, Ken Gaillot <kgail...@redhat.com>
> wrote:
> > On Fri, 2018-02-23 at 16:15 +0530, avinash sharma wrote:
> > > Subject: Switchover of resource(MS) 'RoutingManager' and resource
> > > group 'floatingips',
list sent by peer for local node
> Mar 20 10:55:45 [26932] pcmk3 pacemakerd: info:
> mcp_cpg_deliver: Ignoring process list sent by peer for local node
> Mar 20 10:55:45 [26932] pcmk3 pacemakerd: error:
> pcmk_child_exit: The crmd process (27037) exited: Key has expired
>
info/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.
> pdf
> Bugs: http://bugs.clusterlabs.org
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing li
score="-INFINITY">
>
>
>
The above constraints keep inside-interface on a node where eth1 is
good, and outside-interface on a node where eth2 is good.
I'm guessing you want to keep these two constraints, and start over
from scratch on
direct access to the original
file rather than a copy.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting
uot;**" \
> shutdown_method="immediate" \
> op monitor interval=30s
>
> pcs -f clust_ora_cfg_tmp constraint colocation add ora_db_xe with
> ora_listener INFINITY
> pcs -f clust_ora_cfg_tmp constraint order promote ora_listener then
> st
发件人: Users [mailto:users-boun...@clusterlabs.org] 代表 Ken Gaillot
> 发送时间: 2018年2月23日 23:14
> 收件人: Cluster Labs - All topics related to open-source clustering
> welcomed <users@clusterlabs.org>
> 主题: Re: [ClusterLabs] 答复: 答复: How to configure to make each slave
> resource has one V
ttp://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org
> > ___
> > Users mailing list: Users@clusterlabs.org
> > https://lists.clusterlabs.org/mailman/listinfo/users
> >
> > Project H
On Thu, 2018-06-28 at 09:09 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 27.06.2018 um
> > > > 16:18 in Nachricht
>
> <1530109097.6452.1.ca...@redhat.com>:
> > On Wed, 2018-06-27 at 07:41 +0200, Ulrich Windl wrote:
> > > > >
c features, I'd go with whatever stock packages are
available for libqb and corosync.
knet will be supported by corosync 3 and is bleeding-edge at the moment
(though probably solid). If you do want to compile libqb and/or
corosync, the guide on the wiki grabs the la
oing anything
else. Certain OCF resource agent exit codes are considered "hard"
errors that prevent retrying on the same node: missing dependencies,
file permission errors, etc.
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
http
On Thu, 2018-06-28 at 09:13 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 27.06.2018 um
> > > > 16:32 in Nachricht
>
> <1530109926.6452.3.ca...@redhat.com>:
> > On Wed, 2018-06-27 at 09:18 -0500, Ken Gaillot wrote:
> > > On
Actually, I wouldn't mind getting rid
> > of
> > them altogether in any output.)
> > ‑‑
> > Thanks,
> > Feri
> > ___________
> > Users mailing list: Users@clusterlabs.org
> > https://lists.clusterlabs.org/mailman/listin
;
> Thanks in advance
> Prasad
>
> _______
> Users mailing list: Users@clusterlabs.org
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.c
s a big project and there are many more
pressing issues to address. :-(
There's no workaround within pacemaker, but the setfacl approach sounds
useful.
As a best practice, an agent's meta-data action should not do anything
other than print meta-data. I.e. many agents have common initialization
grotate is
then configured to rotate by moving the log to a new name, sending the
signal, then compressing the old log.
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project
On Thu, 2018-09-27 at 09:58 -0500, Ken Gaillot wrote:
> On Thu, 2018-09-27 at 15:32 +0200, Ferenc Wágner wrote:
> > Christine Caulfield writes:
> >
> > > TBH I would be quite happy to leave this to logrotate but the
> > > message I
> > > was getting
On Thu, 2018-09-27 at 16:09 +0100, Christine Caulfield wrote:
> On 27/09/18 16:01, Ken Gaillot wrote:
> > On Thu, 2018-09-27 at 09:58 -0500, Ken Gaillot wrote:
> > > On Thu, 2018-09-27 at 15:32 +0200, Ferenc Wágner wrote:
> > > > Christine Caulfield writes:
> >
r/lib/ocf/lib/heartbeat/ocf-shellfuncs. These OCFs would fail
> > > miserably.
> > > So before I revisit all our OCFs to check if the well-behave if
> > > called
> > > as non-root, I wanted to check if there is another way.
> > >
> > > Thanks,
&
On Thu, 2018-09-27 at 18:00 +0200, Ferenc Wágner wrote:
> Ken Gaillot writes:
>
> > On Thu, 2018-09-27 at 09:36 +0200, Ulrich Windl wrote:
> >
> > > Obviously you violated the most important cluster rule that is
> > > "be
> > > pa
e also highly relevant. Tighter
integration with these would go a long way toward establishing
longevity.
That brings up another challenge, which is developer resources. It is
difficult to keep up with triaging bug reports much less handling them.
We occasionally have the opportunity to add signif
end turning on debug logging in corosync.conf, and
posting the log here. Hopefully one of the corosync developers can
chime in at that point.
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
P
> > Users mailing list: Users@clusterlabs.org
> > https://lists.clusterlabs.org/mailman/listinfo/users
> >
> > Project Home: http://www.clusterlabs.org
> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratc
> &
Audatex Datos, S.A. | Avda. de Bruselas, 36, Salida
> 16, A‑1 (Diversia) , Alcobendas , Madr
> id, 28108 , Spain On
> 15/10/18 16:27, Ken Gaillot wrote:
> > On Mon, 2018-10-15 at 14:39 +0200, Klaus Wenninger wrote:
> > >
8 249
> | M: +34 619 728 249 |
> franciscojavier.lo...@solera.com | Solera.com
> Audatex Datos, S.A. | Avda. de Bruselas, 36, Salida
> 16, A‑1 (Diversia) , Alcobendas , Madr
> id, 28108 , Spain On
cemaker-cluster? clusterlabs-ha? high-availability?).
The only drawback I see is that it's theoretically possible to deploy a
different membership layer than corosync (in the past others were
supported, and that may happen again in the future), and possible to
run corosync without pacema
> > >
> > > pcs property set stonith-enabled=true
> > >
> > >
> > > Thanks,
> > > Rohit
> > >
> > >
&g
eration is one of the most commonly used
Pacemaker features. You have the flexibility of failing over any
combination of resources you want. Look into clone resources,
master/slave clones, colocation constraints, and the on-fail property
of operations.
--
Ken Gaillot
___
nfo/users
> > >
> > > Project Home: http://www.clusterlabs.org
> > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scra
> > tch.pdf
> > > Bugs: http://bugs.clusterlabs.org
> > >
> >
> > ___
k properly (with no loss of safety).
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_S
801 - 900 of 1686 matches
Mail list logo
