>>> Jonno schrieb am 10.02.2022 um 20:43 in Nachricht
:
> Hello,
>
> I am having some trouble getting my 2 node active/passive cluster to do
> what I want. More specifically, my cluster is removing the VIP from the
> cluster whenever I attempt a failover with a command such as "crm resource
>
>>> "Lentes, Bernd" schrieb am 10.02.2022
>>> um
16:47 in Nachricht
<1736897222.172888317.1644508059181.javamail.zim...@helmholtz-muenchen.de>:
>
> - On Feb 10, 2022, at 4:40 PM, Jehan-Guillaume de Rorthais
> j...@dalibo.com wrote:
>
>>
>> I wonder if after the cluster shutdown
>>> Jehan-Guillaume de Rorthais schrieb am 10.02.2022 um
16:40 in
Nachricht <20220210164000.2e395a37@karst>:
> On Thu, 10 Feb 2022 22:15:07 +0800
> Roger Zhou via Users wrote:
>
>>
>> On 2/9/22 17:46, Lentes, Bernd wrote:
>> >
>> >
>> > - On Feb 7, 2022, at 4:13 PM, Jehan-Guillaume de
Hello,
I am having some trouble getting my 2 node active/passive cluster to do
what I want. More specifically, my cluster is removing the VIP from the
cluster whenever I attempt a failover with a command such as "crm resource
move rsc_cluster_vip node2".
When running the command above, I am
- On Feb 10, 2022, at 4:40 PM, Jehan-Guillaume de Rorthais j...@dalibo.com
wrote:
>
> I wonder if after the cluster shutdown complete, the target-role=Stopped could
> be removed/edited offline with eg. crmadmin? That would make VirtualDomain
> startable on boot.
>
> I suppose this would
On Thu, 10 Feb 2022 22:15:07 +0800
Roger Zhou via Users wrote:
>
> On 2/9/22 17:46, Lentes, Bernd wrote:
> >
> >
> > - On Feb 7, 2022, at 4:13 PM, Jehan-Guillaume de Rorthais
> > j...@dalibo.com wrote:
> >
> >> On Mon, 7 Feb 2022 14:24:44 +0100 (CET)
> >> "Lentes, Bernd" wrote:
> >>
>
On Thu, 10 Feb 2022 15:10:20 +0100
"Ulrich Windl" wrote:
...
> > If you want to gracefully shutdown your cluster, then you can add one
> manual
> > step to first gracefully stop your resources instead of betting the cluster
> > will do the good things.
>
> It's the old discussion: Old HP
On 2/9/22 17:46, Lentes, Bernd wrote:
- On Feb 7, 2022, at 4:13 PM, Jehan-Guillaume de Rorthais j...@dalibo.com
wrote:
On Mon, 7 Feb 2022 14:24:44 +0100 (CET)
"Lentes, Bernd" wrote:
Hi,
i'm currently changing a bit in my cluster because i realized that my
configuration for a power
>>> Jehan-Guillaume de Rorthais schrieb am 10.02.2022 um
10:15 in
Nachricht <20220210101508.768cf643@karst>:
> On Wed, 9 Feb 2022 17:42:35 + (UTC)
> Strahil Nikolov via Users wrote:
>
>> If you gracefully shutdown a node ‑ pacemaker will migrate all resources
away
>> so you need to shut
One drawback of that approach is that adding a the resource stop command will
also prevent the resources from starting once the UPS gets enough power and
start the servers.
Of course a script in cron (@reboot) or in systemd can overcome it.
Best Regards,Strahil Nikolov
On Thu, Feb 10,
On Wed, 9 Feb 2022 17:42:35 + (UTC)
Strahil Nikolov via Users wrote:
> If you gracefully shutdown a node - pacemaker will migrate all resources away
> so you need to shut them down simultaneously and all resources should be
> stopped by the cluster.
>
> Shutting down the nodes would be my
Hi!
just a heads up: Shortly after midnight one of our SLES15 SP3 cluster nodes
started to send SIGSEGV to processes, eventually also to pacemaker, resulting
in a node fence.
I suspect some kernel problem. The configuration was running since a week or so
(since last reboot), however.
(For SP2
12 matches
Mail list logo
