>>> "john tillman" <jo...@panix.com> schrieb am 21.04.2022 um 20:18 in Nachricht <e9e14dceb9c7b4f401fb8e28483cbb0b.squir...@mail.panix.com>: ... > Once the other node is started, something starts the pacemaker service.
Is the pacmemaker started, or does it begin to perform actions once it has a quorum? > pacemaker log starts filling up. journalctl ‑b sees plenty of pacemaker > entires. crm_mon and pcs status are working right and show the cluster in > a good state with all resources started properly. > > So I don't see anything stopping pacemaker from starting at boot. It If it's really pacemaker not starting on boot: Maybe it's waiting for time sync? (Just a thought) > looks like some piece of cluster software is starting it once the second > node is online. Maybe corosync? Although the corosync log doesn't > mention the start of anything. All it logs is seeing the second node > join. > > So what starts pacemaker in this case? systemd usually. What about systemctl status pacemaker (or similar)? Regards, Ulrich _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/