Hi, It seems that ldap timeout caused cluster failure. Cluster is checking status every 15s on master and 16s on slave. Cluster needs postgres user for authentication, but ldap first query user on ldap server and then localy on host. When connection to ldap server was interrupted, cluster couldn't find postgres user and authenticate on db to check state. Problem is solved with reconfiguring /etc/ldap.conf and /etc/nslcd.conf. Following variable is added: nss_initgroups_ignoreusers with specified local users which should be ignored when querying ldap server. Thanks for your help. :) Another problem is that I cannot start postgres master with pacemaker. When I start postgres manually (with systemd) and then start pacemaker on slave, pacemaker is able to recognize master and start slave and failover works. That is another problem which I didn't manage to solve. Should I send a new mail for that issue or we can continue in this thread?
On Fri, 19 Apr 2019 at 19:19, Jehan-Guillaume de Rorthais <[email protected]> wrote: > On Fri, 19 Apr 2019 17:26:14 +0200 > Danka Ivanović <[email protected]> wrote: > ... > > Should I change any of those timeout parameters in order to avoid > timeout? > > You can try to raise the timeout, indeed. But as far as we don't know > **why** > your VMs froze for some time, it is difficult to guess how high should be > these timeouts. > > Not to mention that it will raise your RTO. > -- Pozdrav Danka Ivanovic
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
