Re: [ClusterLabs] Frequent PAF log messages - Forbidding promotion on in state "startup"

Thanks, I should have seen that. I just assumed that everything was working fine because `pcs status` shows no errors. This leads me to another question - is there a way to trigger a rebuild of a slave with pcs? Or do I need to use `pcs cluster stop`, then manually do a new pg_basebackup,

Re: [ClusterLabs] Frequent PAF log messages - Forbidding promotion on in state "startup"

On Mon, 14 May 2018 19:08:47 + "Shobe, Casey" wrote: > > We do not trigger error for such scenario because it would require the > > cluster to react...and there's really no way the cluster can solve such > > issue. So we just put a negative score, which is already

Re: [ClusterLabs] Frequent PAF log messages - Forbidding promotion on in state "startup"

On Mon, 14 May 2018 16:43:52 + "Shobe, Casey" wrote: > Thanks, I should have seen that. I just assumed that everything was working > fine because `pcs status` shows no errors. We do not trigger error for such scenario because it would require the cluster to

Re: [ClusterLabs] Frequent PAF log messages - Forbidding promotion on in state "startup"

On Fri, 11 May 2018 16:25:18 + "Shobe, Casey" wrote: > I'm using PAF and my corosync log ends up filled with messages like this > (about 3 times per minute for each standby node): > > pgsqlms(postgresql-10-main)[26822]: 2018/05/11_06:47:08 INFO: Forbidding >

[ClusterLabs] Frequent PAF log messages - Forbidding promotion on in state "startup"

I'm using PAF and my corosync log ends up filled with messages like this (about 3 times per minute for each standby node): pgsqlms(postgresql-10-main)[26822]: 2018/05/11_06:47:08 INFO: Forbidding promotion on "d-gp2-dbp63-1" in state "startup" pgsqlms(postgresql-10-main)[26822]: