Re: [ClusterLabs] Cluster fails to start on rebooted nodes without manual fiddling...

Hi, thank you very much for your response! > Something comes in mind: did you setup "systemd-tmpfiles" as explained in the > end of the following chapter ? > > https://clusterlabs.github.io/PAF/Quick_Start-Debian-9-pcs.html#postgresql-and-cluster-stack-installation That was it - somehow I

Re: [ClusterLabs] Cluster fails to start on rebooted nodes without manual fiddling...

On Mon, 02 Apr 2018 14:05:09 -0600 Casey & Gina wrote: [...] > Now, if I restart the second node, and execute `pcs cluster start` once it's > back up, it fails to start the resource and shows me this in the `pcs status` > output: > > > -- > *

[ClusterLabs] Cluster fails to start on rebooted nodes without manual fiddling...

Hi! I've set up a couple test Pacemaker/Corosync/PCS clusters on virtual machines to manage a PostgreSQL service using the PostgreSQL Automatic Failover (PAF) resource agent available here: https://clusterlabs.github.io/PAF/ The cluster will be up and running with 3 nodes and PostgreSQL