node to an existing cluster, and it didn’t work as smoothly as
> expected. Cleanly re-adding a node is probably:
>
>1. Cleanly remove a node
>2. Cleanly add a node
>
>
>
> 😉
>
>
>
> Kind regards,
>
> Ulrich Windl
>
>
>
> *From:
e/net/nssdb/qdevice-net-node.p12
>6. Enable or restart corosync-qdevice:
>systemctl enable –now corosync-qdevice.service
>or
>systemctl restart corosync-qdevice.service
>7. Enjoy!
>
>
>
> That’s what practically work for me and included in service script
l disk failure?
>
> Usually a backup is your best friend.
>
>
>
> Kind regards,
>
> Ulrich Windl
>
>
>
> *From:* Users *On Behalf Of *Fabrizio
> Ermini
> *Sent:* Friday, May 9, 2025 4:26 PM
> *To:* users@clusterlabs.org
> *Subject:* [EXT] [ClusterLabs] R
Hi all! Freshmen here, just joined.
I'm currently in the need to rebuild a failed node on a
pacemaker2.1/corosync3.1 2-node cluster with drbd storage.
I've searched in Pacemaker docs and in the list archives, but I haven't
found a clear guide on how to proceed in this task. So far, I've
reinstalle
Hi all! Freshmen here, just joined.
I'm currently in the need to rebuild a failed node on a
pacemaker2.1/corosync3.1 2-node cluster with drbd storage.
I've searched in Pacemaker docs and in the list archives, but I haven't
found a clear guide on how to proceed in this task. So far, I've
reinstalle
Hi!
I am trying to set up an oracle instance managed by a pacemaker cluster.
It's a task that I have performed several times with no issue, but in this
particular case I have a non standard requirement: since the instance
sometimes would take the role of a standby database, the "start" actions
shou
