Hi,
Can you help me with troubleshooting postgres pacemaker cluster failure?
Today cluster failed without promoting secondary to master. At the same
time appeared ldap time out.
Here are the logs, master was stopped by pacemaker at 10:03:40 AM UTC.
Thank you in advance.
corosync.log
Apr 17 10:03
[ postgres-ha-1 ]
Slaves: [ postgres-ha-2 ]
fencing-postgres-ha-1 (stonith:external/ec2): Started postgres-ha-2
fencing-postgres-ha-2 (stonith:external/ec2): Started postgres-ha-1
On Thu, 18 Apr 2019 at 18:24, Jehan-Guillaume de Rorthais
wrote:
> On Thu, 18 Apr 2019 14:19:44 +0200
>
7.3680.952
0.090
*i.will.not.be.e 213.251.128.249 2 u 207 512 377 14.7331.185
0.305
On Fri, 19 Apr 2019 at 11:46, Jehan-Guillaume de Rorthais
wrote:
> On Fri, 19 Apr 2019 11:08:33 +0200
> Danka Ivanović wrote:
>
> > Hi,
> > Thank you for your response.
> &g
a \
stonith-enabled=true \
no-quorum-policy=ignore \
maintenance-mode=false \
last-lrm-refresh=1551885417
rsc_defaults rsc-options: \
resource-stickiness=10 \
migration-threshold=1
Should I change any of those timeout parameters in order to avoid timeout?
On Fri, 19 Apr 2019 at 12:23, Danka Ivanović
wr
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
wrote:
> On Fri, 19 Apr 2019 17:26:14 +0200
> Danka Ivanović wrote:
> ...
> > Should I change any of those timeout parameters in order to avoid
> timeout?
), src=53
Apr 25 16:41:23 [4213] master lrmd: warning:
child_timeout_callback: PGSQL_start_0
process (PID 5986) timed out
Part of the log is attached.
On Tue, 23 Apr 2019 at 17:28, Danka Ivanović
wrote:
> Hi,
> It seems that ldap timeout caused cluster failure. Cluster is checking
> status ev
s://clusterlabs.github.io/PAF/Quick_Start-Debian-9-crm.html
When stonith is enabled and working I imported all other resources and
constraints all together in the same time.
On Fri, 26 Apr 2019 at 13:46, Jehan-Guillaume de Rorthais
wrote:
> Hi,
>
> On Thu, 25 Apr 2019 18:57:55 +0200
&
