L Seems like as of 2019 this is a normal reaction. There looks like there was discussion to find a way to make it automatic but as of now the issue still remains open.
See this issue for the details: https://github.com/ClusterLabs/resource-agents/issues/699 Brian > On 7. May 2023, at 12:56 PM, lejeczek via Users <users@clusterlabs.org> wrote: > > Hi guys. > > I have a resource seemingly running a ok but when a node gets rebooted then > cluster finds it not able, not good to start the resource. > > Failed Resource Actions: > * PGSQL start on podnode3 returned 'error' (My data may be inconsistent. > You have to remove /var/lib/pgsql/tmp/PGSQL.lock file to force start.) at Sun > May 7 11:48:43 2023 after 121ms > > and indeed, with manual intervention, after removal of that file, cluster > seems to be happy to rejoin the node into pgsql cluster. > Is that intentional, by design and if yes/no then why it happens? > > many thanks, L. > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/