[ClusterLabs] PAF / PGSQLMS on Ubuntu

[Jehan-Guillaume de Rorthais]

On Fri, 8 Sep 2023 10:26:42 +0200
lejeczek via Users <users at clusterlabs.org> wrote:

> On 07/09/2023 16:20, lejeczek via Users wrote:
> >
> >
> > On 07/09/2023 16:09, Andrei Borzenkov wrote:  
> >> On Thu, Sep 7, 2023 at 5:01 PM lejeczek via Users 
> >> <users at clusterlabs.org> wrote:  
> >>> Hi guys.
> >>>
> >>> I'm trying to set ocf_heartbeat_pgsqlms agent but I get:
> >>> ...
> >>> Failed Resource Actions:
> >>>    * PGSQL-PAF-5433 stop on ubusrv3 returned 'invalid 
> >>> parameter' because 'Parameter "recovery_target_timeline" 
> >>> MUST be set to 'latest'. It is currently set to ''' at 
> >>> Thu Sep  7 13:58:06 2023 after 54ms
> >>>
> >>> I'm new to Ubuntu and I see that Ubuntu has a bit 
> >>> different approach to paths (in comparison to how Centos 
> >>> do it).
> >>> I see separation between config & data, eg.
> >>>
> >>> 14  paf     5433 down   postgres 
> >>> /var/lib/postgresql/14/paf 
> >>> /var/log/postgresql/postgresql-14-paf.log
> >>>
> >>> I create the resource like here:
> >>>  
> >>> -> $ pcs resource create PGSQL-PAF-5433   
> >>> ocf:heartbeat:pgsqlms pgport=5433 bindir=/usr/bin 
> >>> pgdata=/etc/postgresql/14/paf 
> >>> datadir=/var/lib/postgresql/14/paf meta 
> >>> failure-timeout=30s master-max=1 op start timeout=60s op 
> >>> stop timeout=60s op promote timeout=30s op demote 
> >>> timeout=120s op monitor interval=15s timeout=10s 
> >>> role="Promoted" op monitor interval=16s timeout=10s 
> >>> role="Unpromoted" op notify timeout=60s promotable 
> >>> notify=true failure-timeout=30s master-max=1 --disable
> >>>
> >>> Ubuntu 22.04.3 LTS
> >>> What am I missing can you tell?  
> >> Exactly what the message tells you. You need to set 
> >> recovery_target=latest.  
> > and having it in 'postgresql.conf' make it all work for you?
> > I've had it and got those errors - perhaps that has to be 
> > set some place else.
> >  
> In case anybody was in this situation - I was missing one 
> important bit: _bindir_
> Ubuntu's pgSQL binaries have different path - what 
> resource/agent returns as errors is utterly confusing.

Uh ? Good point, I'll definitely have to check that.

Thanks for the report!