Thread

Patroni Issue

Inzamam Shafiq <inzamam.shafiq@hotmail.com> — 2023-05-10T12:03:13Z

Hi Team,

I hope you are doing well.

I am working on patroni auto failover, I have 3 ETCD nodes, 2 pgsql/patroni nodes, ETCD cluster is running fine with no issues, now I have installed postgresql on patroni nodes and configured streaming replication using pg_basebackup, which is running fine. On top of that I have created yaml file for patroni, when I start patroni on the first(primary) node, it show the following logs and keep on showing this message and stay in starting state. can someone please help me to identify the issue, logs are as follows,

-bash-4.2$ patroni /etc/patroni/patroni.yml
2023-05-10 16:43:59,147 INFO: Selected new etcd server http://172.xx.xx.xx:2379
2023-05-10 16:43:59,151 INFO: No PostgreSQL configuration items changed, nothing to reload.
2023-05-10 16:43:59,171 WARNING: Postgresql is not running.
2023-05-10 16:43:59,171 INFO: Lock owner: None; I am pg1
2023-05-10 16:43:59,174 INFO: pg_controldata:
  pg_control version number: 1201
  Catalog version number: 201909212
  Database system identifier: 7230768165275119881
  Database cluster state: shut down
  pg_control last modified: Wed May 10 16:43:54 2023
  Latest checkpoint location: 0/6000150
  Latest checkpoint's REDO location: 0/6000150
  Latest checkpoint's REDO WAL file: 000000010000000000000006
  Latest checkpoint's TimeLineID: 1
  Latest checkpoint's PrevTimeLineID: 1
  Latest checkpoint's full_page_writes: on
  Latest checkpoint's NextXID: 0:490
  Latest checkpoint's NextOID: 16386
  Latest checkpoint's NextMultiXactId: 1
  Latest checkpoint's NextMultiOffset: 0
  Latest checkpoint's oldestXID: 479
  Latest checkpoint's oldestXID's DB: 1
  Latest checkpoint's oldestActiveXID: 0
  Latest checkpoint's oldestMultiXid: 1
  Latest checkpoint's oldestMulti's DB: 1
  Latest checkpoint's oldestCommitTsXid: 0
  Latest checkpoint's newestCommitTsXid: 0
  Time of latest checkpoint: Wed May 10 16:43:53 2023
  Fake LSN counter for unlogged rels: 0/3E8
  Minimum recovery ending location: 0/0
  Min recovery ending loc's timeline: 0
  Backup start location: 0/0
  Backup end location: 0/0
  End-of-backup record required: no
  wal_level setting: replica
  wal_log_hints setting: on
  max_connections setting: 100
  max_worker_processes setting: 8
  max_wal_senders setting: 5
  max_prepared_xacts setting: 0
  max_locks_per_xact setting: 64
  track_commit_timestamp setting: off
  Maximum data alignment: 8
  Database block size: 8192
  Blocks per segment of large relation: 131072
  WAL block size: 8192
  Bytes per WAL segment: 16777216
  Maximum length of identifiers: 64
  Maximum columns in an index: 32
  Maximum size of a TOAST chunk: 1996
  Size of a large-object chunk: 2048
  Date/time type storage: 64-bit integers
  Float4 argument passing: by value
  Float8 argument passing: by value
  Data page checksum version: 0
  Mock authentication nonce: c557e5f51c201ffaa61d5372fe87384044552322ff979d1e05f6030be1fc7cc0

2023-05-10 16:43:59,185 INFO: Lock owner: None; I am pg1
2023-05-10 16:43:59,191 INFO: starting as a secondary
2023-05-10 16:43:59.461 PKT [22878] LOG:  starting PostgreSQL 12.14 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
2023-05-10 16:43:59.461 PKT [22878] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-05-10 16:43:59,476 INFO: postmaster pid=22878
2023-05-10 16:43:59.479 PKT [22878] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
localhost:5432 - no response
2023-05-10 16:43:59.498 PKT [22878] LOG:  redirecting log output to logging collector process
2023-05-10 16:43:59.498 PKT [22878] HINT:  Future log output will appear in directory "log".
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
2023-05-10 16:44:09,163 INFO: Lock owner: None; I am pg1
2023-05-10 16:44:09,163 INFO: not healthy enough for leader race
2023-05-10 16:44:09,169 INFO: restarting after failure in progress
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response
2023-05-10 16:44:19,163 INFO: Lock owner: None; I am pg1
2023-05-10 16:44:19,163 INFO: not healthy enough for leader race
2023-05-10 16:44:19,169 INFO: restarting after failure in progress
localhost:5432 - no response
localhost:5432 - no response
localhost:5432 - no response

Thanks.

Regards,

Inzamam Shafiq
Sr. DBA