On Tue, 30 Apr 2019 17:28:44 +0200
Danka Ivanović <[email protected]> wrote:
> Hi, I tried new clean config with upgraded postgres and corosync and
> pacemaker packages.
In this attempt, your PostgreSQL resource timed out while starting up:
Apr 30 15:09:43 [13342] master lrmd: debug: operation_finished:
PGSQL_start_0:13864:stdout [ FATAL: the database system is starting
up ]
Apr 30 15:09:43 [13342] master lrmd: info: log_finished:
finished - rsc:PGSQL action:start call_id:21 pid:13864 exit-code:1
exec-time:60003ms queue-time:0ms
Apr 30 15:09:43 [13345] master crmd: debug:
create_operation_update: do_update_resource: Updating resource PGSQL
after start op Timed Out (interval=0)
I suppose your local instance had many WAL to replay before being consistent
and accepting connections and the 60s timeout wasn't enough.
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
