the addressee whose name is specified above. Should you receive
> this message by mistake, we would be most grateful if you informed us
> that the message has been sent to you. In this case, we also ask that
> you delete this message from your mailbox, and do not forw
On Mon, 2023-04-10 at 16:33 +0300, Andrei Borzenkov wrote:
> On Mon, Apr 10, 2023 at 4:26 PM Ken Gaillot
> wrote:
> > On Mon, 2023-04-10 at 14:18 +0300, Miro Igov wrote:
> > > Hello,
> > > I have a resource with location constraint set to:
> > >
> >
ssage by mistake, we would be most grateful if you informed us
> that the message has been sent to you. In this case, we also ask that
> you delete this message from your mailbox, and do not forward it or
> any part of it to anyone else.
> Thank you for your cooperation
yone loves basing rules on the phase of the moon, now is the time
to speak up :)
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
,now 2.1.2-1ubuntu3 amd64 [installed]
> pcs/jammy,now 0.10.11-2ubuntu3 all [installed]
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
--
Ken Gaillot
___
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 att
ation.
Corosync's cluster membership protocol handles the heartbeat; CPG is a
cluster messaging protocol, allowing cluster nodes to send data to each
other, so it depends on what uses CPG. In this case, Pacemaker uses CPG
for sensitive data.
>
> Thanks
or 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.
If sbd is in use, it will kick in and reboot the node. However without
sbd, there is no autom
On Tue, 2023-03-21 at 15:18 -0500, Ken Gaillot wrote:
> Hi all,
>
> Pacemaker has always supported letting users add arbitrary
> descriptions
> to resources, but doing so required low-level XML changes.
>
> With the Pacemaker 2.1.6 release expected in a couple of month
tion value=Floating IP for database client access
Query the description for a resource:
# crm_resource -r ip1 --get-parameter description
Floating IP for database client access
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.o
a new alert
meta-data attribute, "enabled", which defaults to "true" and can be set
to "false".
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
suspicious
attachment and fake "unsubscribe" link.
I don't know if they're targeting list posters more broadly, but it's
something to keep an eye out for.
The hostile message I received started with the nonsense line "Pleaase
begin the attached agreement checking process photos in f
>name="standby" value="on"/>
>
>
>
>
>
>name="standby" value="on"/>
>
>
>
>
>name="standby" value="on"/>
>
ite intermittent and observed on other nodes as well.
> We have seen a similar issue when we try to remove the node from
> standby mode (using crm node online) command. One/more nodes fails to
> get removed from standby mode.
>
> We suspect it could be an issue with parallel execution of node
> standby/online command for all nodes but this issue wasn't observed
> with pacemaker packaged with SLES15 SP2 OS.
>
> I'm attaching the pacemaker.log from FILE-2 for analysis. Let us know
> if any additional information is required.
>
> OS: SLES15 SP4
> Pacemaker version -->
> crmadmin --version
> Pacemaker 2.1.2+20211124.ada5c3b36-150400.2.43
>
> Thanks,
> Ayush
>
> ___
> 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/
! have_binary
> > "crm_master";
> > then
> > ${HA_SBIN_DIR}/crm_attribute -p
> > $OCF_RESOURCE_INSTANCE $@
> > else
> > ${HA_SBIN_DIR}/crm_master -l reboot $@
> > fi
> > (snip)
> >
> >
> > This content has also been registered in the following Bugzilla:
> > https://bugs.clusterlabs.org/show_bug.cgi?id=5509
> >
> > Best Regards,
> > Hideo Yamauchi.
> >
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
t;
> any suggestions on the cause of the error, or at least where to start
> debugging, are welcome.
>
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
to the "Offline" under "PCSD Status", yes, that's
normal. That only affects the pcsd daemon used to coordinate pcs
commands across all nodes, not the cluster itself. As far as I know,
pcsd has no way to use multiple links.
The "online" under "Nodes" is what's rel
09:43:27 server3 ntpd[602]: Listen normally on 8 eth0
> 10.13.68.12:123
> Feb 15 09:43:27 server3 ntpd[602]: new interface(s) found: waking up
> resolver
> => Feb 15 09:43:28 server3 pacemaker-controld[862]: notice: Result
> of start operation for tomcat9 on server3: ok
> Feb 15 09:43:29 server3 corosync[568]: [KNET ] pmtud: PMTUD link
> change for host: 2 link: 0 from 485 to 1397
> Feb 15 09:43:29 server3 corosync[568]: [KNET ] pmtud: PMTUD link
> change for host: 1 link: 0 from 485 to 1397
> Feb 15 09:43:29 server3 corosync[568]: [KNET ] pmtud: Global data
> MTU changed to: 1397
> => Feb 15 09:43:29 server3 pacemaker-controld[862]: notice:
> Requesting local execution of stop operation for tomcat9 on server3
>
> Any idea ?
What do the logs on the other node say over the same time frame?
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Tue, 2023-02-07 at 07:57 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 06.02.2023 um
> > > > 16:29 in Nachricht
> <1fc864736b788762d00fbc0b78da1b34fc1137d3.ca...@redhat.com>:
> > Hi all,
> >
> > Node attributes will rec
can be compared against 3.17.4 to
determine support.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
do a new cluster instead is if you want to do
> some
> > testing before making it live.
> > --
> > Ken Gaillot
>
>
> thanks for your answer. So upgrading detached nodes will result in
> downtime of haproxy and may disclose some other surprises...
> I thin
> Or do you suggest building a new cluster with new servers, because
> versions from 18.04/20.04 differ to much?
>
> Thank you,
> Hajo
While the Pacemaker versions support rolling upgrades, those Corosync
versions do not, so you'll have to do the detach-and-reattach
set a timestamp on the node where the resource is currently
> active before doing crm_standby and select the node with the oldest
> timestamp (I do not think pacemaker supports such computation in its
> rules).
You could do it entirely with rules without needing the cron.
C
this point, another node would fence this one due to the
stop failure.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
likely
> > to
> > build against centos stream 8 I could try? If not, do you know the
> > command off and hand to create the rpm's from source? If not, I'll
> > grab
> > the source and read the docs for configure.
>
> Never mind, I've got it building. Will test shortly.
FYI, you can run "make -C rpm rpm" from a source checkout.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
> Can you please tell me if this type of installation might cause any
> issue?
>
>
> Regards
> Piotr Jelen
> Senior Systems Platform Engineer
>
> Mastercard
> Mountain View, Central Park | Leopard
--
Ken Gaillot
___
Ma
meter notify=true
> for your master resource
> Error: Errors have occurred, therefore pcs is unable to continue
pcs now runs an agent's validate-all action before creating a resource.
In this case it's detecting a real issue in your command. The options
you have after "meta" are c
On Wed, 2022-12-21 at 10:45 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 20.12.2022 um
> > > > 16:21 in
> Nachricht
> <3a5960c2331f97496119720f6b5a760b3fe3bbcf.ca...@redhat.com>:
> > On Tue, 2022‑12‑20 at 11:33 +0300, Andrei Borzenkov wro
did,
so resources can't be recovered. It could work with sbd, but the poster
said that the physical hosts aren't accessible.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
uses this type of error.
>
> Best regards,
>
> Thomas Cas | Technicien du support infogérance
> PHONE : +33 3 51 25 23 26 WEB : www.ikoula.com/en
> IKOULA Data Center 34 rue Pont Assy - 51100 Reims - FRANCE
> Before printing this letter, think about the impact on
ws or opinions presented in this email are solely
> those of the author and do not necessarily represent those of the
> company.
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlab
server), not pacemaker. With this design, if one
site loses network access, it will shut itself down, and fencing only
needs to be able to work locally at each site.
https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/singlehtml/index.html#document-multi-site-clusters
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
, Grace Chin, Hideo Yamauchi, Jan Pokorný, Ken Gaillot, Klaus
Wenninger, lihaipeng, luckhuanhuan, Petr Pavlu, Reid Wahl, Taketo Kabe,
wangluwei, and wangmeng.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
tps://alteeve.com/
> >
> > ___
> > 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/
.4.git.el8.x86_64
> pacemaker-libs-2.1.4-1.2.1.4.git.el8.x86_64
> pacemaker-cli-2.1.4-1.2.1.4.git.el8.x86_64
>
> Please let us know once it is fixed on 2.1.5-rc3 ,we need to build
> rpm without git checkout method.
>
> Thanks and Regards,
> S Sathish S
> -Original Message--
and simulations, but we can't cover all
possible use cases, so your feedback is important and appreciated.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
r: Child returned status 1
> /usr/bin/tar: Error is not recoverable: exiting now
> error: Bad exit status from /var/tmp/rpm-tmp.fb1j8n (%prep)
>
>
> RPM build errors:
> File /root/smf_source/pacemaker-Pacemaker-2.1.4/pacemaker-
> DIST.tar.gz is smaller than 13 bytes
the new release.
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 Chris Lumens, Gao,Yan, and Ken Gaillot.
--
Ken Gaillot
gt; # Address of first link
> ring0_addr: node-2
> # When knet transport is used it's possible to define up to 8
> links
> ring1_addr: 60.60.60.119
> }
> # ...
> service {
> var: 0
> name: pacemaker
> }
> }
>
>
>
>
> Attached is the log in debug mode
> ___
> 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/
the running
> Live-Migration and would have start the shutdown when the Live-
> Migration is finished ?
>
> Bernd
>
Yep. It's not specific to migration -- any actions already initiated
have to finish before the cluster will do anything new, because
Hi everybody,
Just FYI, the clusterlabs.org server (including the websites and
mailing lists) will be taken down for planned maintenance this weekend.
Most likely it will just be a few hours on Saturday, but if there are
complications it could be longer.
--
Ken Gaillot
On Fri, 2022-10-21 at 13:05 +0200, Lentes, Bernd wrote:
> - On 17 Oct, 2022, at 21:41, Ken Gaillot kgail...@redhat.com
> wrote:
>
> > This turned out to be interesting.
> >
> > In the first case, the resource history contains a start action and
> > a
>
lt; [
> > > mailto:users@clusterlabs.org | users@clusterlabs.org ] > wrote:
> >
> >
> >
> > > Did you try a cleanup in between?
> >
> > When i do a cleanup before trace/untrace the resource is not
> > restarted.
> > When i don't do a cleanup it is restarted.
> >
> > Bernd
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
to all contributors of source code to this release,
including bin-ly, Chris Lumens, Christine Caulfield, Ferenc Wágner,
Gao,Yan, Grace Chin, Hideo Yamauchi, Jan Pokorný, Ken Gaillot, Klaus
Wenninger, lihaipeng, luckhuanhuan, Petr Pavlu, Reid Wahl, Taketo Kabe,
wangluwei, and wangmeng.
--
Ken Gaillot
On Tue, 2022-10-18 at 20:48 +0200, Lentes, Bernd wrote:
> - On 17 Oct, 2022, at 21:41, Ken Gaillot kgail...@redhat.com
> wrote:
>
> > This turned out to be interesting.
> >
> > In the first case, the resource history contains a start action and
> > a
>
l (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-genetrap (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-mouseidgenes (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-greensql (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-severin (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave ping_19216810010(Stopped)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave ping_19216810020(Stopped)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm_crispor (Stopped unmanaged)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-dietrich (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-pathway (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-crispor-server (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-geneious-license (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-nc-mcd (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-amok (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-geneious-license-mcd (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-documents-oo (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave fs_test_ocfs2 (Started ha-idg-2)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-ssh (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm_snipanalysis (Stopped unmanaged)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-seneca (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-photoshop(Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-check-mk (Started ha-idg-1)
> Oct 14 19:26:33 [26000] ha-idg-1pengine: info:
> LogActions: Leave vm-encore (Started ha-idg-1)
>
> no restart !!!
>
> There is only one difference i see is the section i marked with "--
> ".
> But i don't understand why this is different.
>
> Bernd
> ___
> 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/
two files, I can try to figure out what happened.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
tion about
> DLM, because it is a mystery for me.
> Sometimes the DLM does not respond to the "monitor", so it needs to
> be restarted, and therefore all depending resources (which is a lot).
> This happens under some load (although not completely overwhelmed).
>
> Thank
_
> 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/
6AM -0500, Ken Gaillot wrote:
> > On Thu, 2022-09-08 at 15:01 +0200, Lars Ellenberg wrote:
> > > Scenario:
> > > three nodes, no fencing (I know)
> > > break network, isolating nodes
> > > unbreak network, see how cluster partitions rejoin and resume
> &
an optional "name"
attribute to use instead of the XML ID. If no name is specified, it
will continue to use the XML ID, maintaining backward compatibility.
The release will also have a few other small features and a bunch of
bug fixes, including multiple regression fixes.
--
K
t just override the
join state if the other nodes think it is different, but we could
release DC and restart the join process. How did it handle the
situation in this case?
>
> Thanks,
> Lars
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
ll get started
after the primary resource *if* they both need to be started, but if
only one needs to be started, the other won't be affected.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
loss.
If your cluster nodes are virtual machines, and you have access to the
host, this should work:
https://wiki.clusterlabs.org/wiki/Guest_Fencing
If you're using something else as cluster nodes, let us know.
--
Ken Gaillot
___
Manage your subs
resource agent, and record the result if changed.
When resource loss is detected, the stop/start time of the resource is
the main factor.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
(ocf::lentes:VirtualDomain):Started ha-idg-1 <===
> Aug 03 00:14:04 [19367] ha-idg-1pengine: info:
> common_print:vm-
> photoshop(ocf::lentes:VirtualDomain):Started ha-idg-1
> Aug 03 00:14:04 [19367] ha-idg-1pengine: info:
> common_print:vm-check-
&
NOUE
I agree, it makes sense to use O_DIRECT when available. I don't think
an option is necessary.
However, O_DIRECT is not available on all OSes, so the configure script
should detect support. Also, it is not supported by all filesystems, so
if the open fails, we should retry without O_DIRECT.
--
K
a quorum device? I
> have 2 node cluster with one quorum device. Both 2 nodes have fencing
> agents.
>
> But I wonder that should i define the fencing agent for quorum device
> or not? Just in case it is laggy...
>
> Thank you so much!
>
.
Live migration is a multi-step process, so it is possible for the
process to get interrupted in the middle, but in that case the resource
will likely be restarted.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/list
Quick update: I believe only the redis and rabbitmq agents were
affected, so most users don't have to care about this issue.
On Mon, 2022-06-27 at 16:07 -0500, Ken Gaillot wrote:
> Hi all,
>
> Another regression was found that was introduced in Pacemaker 2.1.3.
>
> As part of
esources are advised to wait until
the fix is released (expected in 2.1.5 at the end of this year) or
ensure that their OS packages include the fix if using 2.1.3 or 2.1.4.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/ma
e metadata section to be the
> > same as the filename.
> >
> >
> > Oyvind
> >
>
> OMG. Thank you !!!
>
> Bernd
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
s://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/
nodes, and just want to
run resources inside containers, then bundles are your best bet:
https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/singlehtml/index.html#bundles-containerized-resources
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
Lumens, Ken Gaillot, Petr Pavlu, and Reid Wahl.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Tue, 2022-06-14 at 15:53 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 14.06.2022 um
> > > > 15:49 in
> Nachricht
> :
> > On Tue, 2022‑06‑14 at 14:36 +0200, Ulrich Windl wrote:
> > > Hi!
> > >
> > > I had a cas
n 14 14:09:16 h19 pacemaker-schedulerd[7442]: notice: *
> Recoverprm_xen_v04 ( h19 )
>
> Regards,
> ulrich
>
>
>
> ___
> Manage your subscription:
> https://lis
re any impact on cluster functionality?
> Thanks
> Priyanka
>
It is fine for the DC to be NONE briefly, but if it lasts more than a
few seconds, something's wrong. The logs should have more details.
The cluster is unable to manage resources or fence nodes when there is
no DC. Effectively i
ainerized-resources
>
> Regards
> Sridhar
>
>
> On Wed, 8 Jun 2022 at 19:46, Andrei Borzenkov
> wrote:
> > On 08.06.2022 17:01, Ken Gaillot wrote:
> > > On Wed, 2022-06-08 at 18:31 +0530, Sridhar K wrote:
> > >> Hi Team,
> > >>
> &g
her the above scenario can be handled, any
> links, examples would be of great help.
>
> Attaching a picture that depicts the scenario.
>
> Please do the needful, Thank you
>
> Regards
> Sridhar
--
Ken Gaillot
___
Manage your
is important and appreciated.
Many thanks to all contributors of source code to this release,
including Chris Lumens, Ken Gaillot, Petr Pavlu, and Reid Wahl.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
is why it wasn't caught before release.
A 2.1.4 release with the fix should be available next week.
In the meantime, 2.1.3 is perfectly fine for clusters that don't use
target-attribute.
--
Ken Gaillot
___
Manage your subscription:
https
colorized for a user's ACLs.
Many thanks to all contributors of source code to this
release, including Chris Lumens, Chrissie Caulfield, Gao,Yan, Grace
Chin, Hideo Yamauchi, Jan Friesse, Jan Pokorný, Ken Gaillot, Klaus
Wenninger, Liang,Xin, Reid Wahl, Tomas Jelinek, and Wangluwei.
--
Ken Gaillot
ing0_addr (str) = k2
> nodelist.node.2.nodeid (u32) = 3
> nodelist.node.2.ring0_addr (str) = k3
>
> Why not also use "uname -n" when "name" is not explicitly set in the
> corosync nodelist config?
> ___
> 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/
>
> What is the cleanup step (or steps) that I'm missing? Or are there so
> many details that it's best to leave this to pcs/crmsh?
crm_node --remove node1
or just don't start pacemaker until corosync is correct. pcs/crmsh are
definitely much easier to use (especially as the number of nodes grows)
but if you're looking to learn low-level details, there's nothing wrong
with that.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
> > [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg
> > ] <http://www.aciworldwide.com>
> > This email message and any attachments may contain confidential,
> > proprietary or non-public information. The information is intended
> > solely for the designated
Gaillot, and Reid Wahl.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
set it. I'm not familiar enough with that agent to know why it
might not.
>
>
>
> Atenciosamente/Kind regards,
> Salatiel
>
> On Mon, May 2, 2022 at 12:26 PM Ken Gaillot
> wrote:
> > On Mon, 2022-05-02 at 09:58 -0300, Salatiel Filho wrote:
> > > Hi, I am trying to unders
r in
that situation. There must be something else in the configuration that
is preventing promotion.
The DRBD resource agent should set a promotion score for the node. You
can run "crm_mon -1A" to show all node attributes; there should be one
like "master-DRBDData" for the active
ften 16 or
32 full cluster nodes (more are possible with Pacemaker Remote).
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Wed, 2022-04-27 at 08:49 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 26.04.2022 um
> > > > 21:24 in
> Nachricht
> :
> > On Tue, 2022‑04‑26 at 15:20 ‑0300, Salatiel Filho wrote:
> > > I have a question about OCF_TIMEOUT. Some time
ware_rest): Started
> server01
> ...
>
> Is "pcs resource cleanup" the right way to remove those messages ?
>
>
>
>
> Atenciosamente/Kind regards,
> Salatiel
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
, Chrissie Caulfield, Gao,Yan, Grace Chin, Hideo
Yamauchi, Jan Friesse, Jan Pokorný, Ken Gaillot, Klaus Wenninger,
Liang,Xin, Reid Wahl, Tomas Jelinek, and Wangluwei.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo
iceMasterWins:
> No
>
> Is there something specific I should look for in the log?
>
> So can a two node cluster work after booting only one node? Maybe it
> never will and I am wasting a lot of time, yours and mine.
>
> If it can, what else can I investigate further?
>
> Best regards,
> John
>
What does crm_mon show when the node is up by itself?
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
require manual
intervention again to get going.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Wed, 2022-04-13 at 08:22 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 12.04.2022 um
> > > > 17:22 in
> Nachricht
> <33f4147d0f6a3e46581aaa46a4eca81dfa59ce15.ca...@redhat.com>:
> > Hi all,
> >
> > I'm hoping to have the
resources,
but not know why, unless you thought to check every node health
attribute.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Mon, 2022-04-11 at 08:20 +0200, Ulrich Windl wrote:
> > > > Andrei Borzenkov schrieb am 09.04.2022 um
> > > > 06:48 in
> Nachricht <30178b34-d2fd-1af4-58ed-d9d2aa6e6...@gmail.com>:
> > On 08.04.2022 20:16, Ken Gaillot wrote:
> > > Hi all,
&
ose
other resources will still need to be fully restarted. This is because
any ordering constraint "start A then start B" implies "stop B then
stop A", so we can't stop the wrongly active instances of A until B is
stopped.
--
Ken Gaillot
_
lone-node-max=1 target-role=Started interleave=true
> colocation col_saphana_ip_HPN_HDB00 4000: g_ip_HPN_HDB00:Started
> msl_SAPHana_HPN_HDB00:Master
> order ord_SAPHana_HPN_HDB00 Optional: cln_SAPHanaTopology_HPN_HDB00
> msl_SAPHana_HPN_HDB00
> property cib-bootstrap-options: \
> last-lrm-refresh=16493
931] for device 'fence-sbd' returned: -61 (No
> data available)
> Apr 6 14:40:46 ubuntuserver pacemaker-fenced[349712]: warning: fence-
> sbd:349931 [ Performing: stonith -t external/sbd -E -S ]
> Apr 6 14:40:46 ubuntuserver pacemaker-fenced[349712]: warning: fence-
> sbd:349931 [
at2
> x.x.x.2 z2-server-nat1
> ...
> ...
>
> -----------
> -
>
> I've also made sure the service is up:
>
> [user1@z2-server-nat2 ~]$ systemctl status pcsd.service
> ● pcsd.service - PCS GUI and remote configuration interface
>Loaded: loaded (/usr/lib/systemd/system/pcsd.service; enabled;
> vendor preset: disabled)
>Active: active (running) since Tue 2022-04-05 04:29:16 GMT; 3h
> 24min ago
> Docs: man:pcsd(8)
>man:pcs(8)
> Main PID: 856 (pcsd)
>Memory: 28.6M
>CGroup: /system.slice/pcsd.service
>└─856 /usr/bin/ruby /usr/lib/pcsd/pcsd
>
> Apr 05 04:29:16 z2-server-nat2 systemd[1]: Starting PCS GUI and
> remote configuration interface...
> Apr 05 04:29:16 z2-server-nat2 systemd[1]: Started PCS GUI and remote
> configuration interface.
>
> ---
> -
>
> Am I missing something in making the nodes able to communicate with
> each other? How do I proceed from here?
>
> Regards,
> Chariot
> ___
> 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/
labs.org/pacemaker/doc/2.1/Pacemaker_Explained/singlehtml/index.html#resource-expressions
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
ly start the second resource if the first failed to
> > > start. There
> > > is no timeout option.
> > >
> > > Best regards,
> > > -John
> > >
> >
> > How do you envision the timeout working?
> >
> > You can add a timeou
gt; start. There
> is no timeout option.
>
> Best regards,
> -John
>
How do you envision the timeout working?
You can add a timeout for the ordering itself using rules, where the
ordering no longer applies after a certain date/time, but it doesn't
sound like that's what you want.
to keeping crm_report
around? :-) It would remain available for a long transition period to
give time for the updated sosreport plugins to make their way into
distros and for higher-level tools and user scripts to be updated.
--
Ken Gaillot
___
Manage your
ch a case can re-occur inspite
> of stonith already configured. Hence the ask .
> In case this situation gets reproduced, how can it be handled?
>
> Note: We have stonith configured and it has been working fine so far.
> In this case also, the initial fencing happened from stonith only.
>
> Thanks in advance!
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Mon, 2022-03-21 at 08:27 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 18.03.2022 um
> > > > 13:39 in
> Nachricht
> :
> > On Fri, 2022‑03‑18 at 08:46 +0100, Ulrich Windl wrote:
> > > Hi!
> > >
> > > Parsing the ou
__
> 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/
of the CIB that the specified user can't see.
This feature was initially developed by Jan Pokorný and completed by
Grace Chin.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs h
101 - 200 of 1689 matches
Mail list logo
