I have a two-node cluster, meqfc0 and meqfc1. When both nodes are up, the
cluster will run OK on either meqfc0 or meqfc1.
My practice for OS patching is to patch the inactive node, migrate, then patch
the formerly active node. Patching requires a reboot.
The cluster has run peacefully with
I have reworked csync2's SSL keys, and I was able to use ha-cluster-join to add
the second node to the cluster. Thank you for the guidance!
However, not all the resources are happy with this.
eagnmnmeqfc1:/var/lib/pacemaker/cib # crm status
Stack: corosync
Current DC: eagnmnmeqfc0 (version
Hello.
I am trying to setup a two-node cluster of SLES12SP4 servers. The two nodes
are named 'eagnmnmeqfc0', IP 56.76.161.34, and 'eagnmnmeqfc1', IP 56.76.161.35
The ha-cluster-init on fc0 went fine. It is set up for unicast, as multicast
is blocked on our networks.
The cluster-join on fc1
With respect, I've given up on the ocf:heartbeat:apache module.
I've set up my Apache resource with:
# systemctl disable apache2
# crm configure primitive ncoa_apache systemd:apache2
# crm configure modgroup grp_ncoa add ncoa_apache
# crm configure show ncoa_apache
primitive ncoa_apache systemd:
>mailto:kgail...@redhat.com]
>Sent: Monday, October 14, 2019 12:02 PM
>
>If you have SELinux enabled, check for denials. The cluster processes have a
>different SELinux context than systemd, so policies might not be set up
>correctly.
>--
>Ken Gaillot
Alas, SELinux is not in use.
I am thin
> If pacemaker is managing a resource, the service should not be enabled to
> start on boot (regardless of init or systemd). Pacemaker will start and stop
> the service as needed according to the cluster configuration.
Apache startup is disabled in systemctl, and there is no apache script in
/
Good morning.
I've just upgraded a two-node active-passive cluster from SLES11 to SLES12.
This means that I've gone from /etc/init.d scripts to systemd services.
On the SLES11 server, this worked:
I had to
