<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">L<div><br></div><div>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. </div><div><br></div><div>See this issue for the details:</div><div><br></div><div><a href="https://github.com/ClusterLabs/resource-agents/issues/699">https://github.com/ClusterLabs/resource-agents/issues/699</a><br><br>Brian</div><div><br></div><div><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite">On 7. May 2023, at 12:56 PM, lejeczek via Users <users@clusterlabs.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<font size="2"><font face="Courier 10 Pitch">Hi guys.<br>
<br>
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.<br>
<br>
Failed Resource Actions:<br>
* 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<br>
<br>
and indeed, with manual intervention, after removal of that
file, cluster seems to be happy to rejoin the node into pgsql
cluster.<br>
Is that intentional, by design and if yes/no then why it
happens?<br>
<br>
many thanks, L.<br>
</font></font>
<span>_______________________________________________</span><br><span>Manage your subscription:</span><br><span>https://lists.clusterlabs.org/mailman/listinfo/users</span><br><span></span><br><span>ClusterLabs home: https://www.clusterlabs.org/</span><br></div></blockquote></div></body></html>