EnterpriseDB/repmgr

wrong upstream in witness

Opened this issue · 1 comments

After some switchovers and a fail test my witness have a wrong Upstream at repmgr cluster show

its is a know issue ?

-bash-4.2$ repmgr cluster show;
 ID | Name | Role    | Status    | Upstream | Location | Priority | Timeline | Connection string
----+------+---------+-----------+----------+----------+----------+----------+-------------------------------------------------------
 1  | pg01 | primary | - failed  | ?        | default  | 100      |          | host=pg01 user=repmgr dbname=repmgr connect_timeout=2
 2  | pg02 | primary | * running |          | default  | 100      | 10       | host=pg02 user=repmgr dbname=repmgr connect_timeout=2
 3  | wn01 | witness | * running | ? pg01   | default  | 0        | n/a      | host=wn01 user=repmgr dbname=repmgr connect_timeout=2

WARNING: following issues were detected

  • unable to connect to node "pg01" (ID: 1)
  • unable to connect to node "wn01" (ID: 3)'s upstream node "pg01" (ID: 1)

HINT: execute with --verbose option to see connection error messages
-bash-4.2$ hostname
wn01

repmgr=# select CURRENT_TIMESTAMP, node_id, type, upstream_node_id, get_upstream_node_id() from nodes where node_id = get_local_node_id();
       current_timestamp       | node_id |  type   | upstream_node_id | get_upstream_node_id
-------------------------------+---------+---------+------------------+----------------------
 2022-09-07 21:06:01.458363-04 |       3 | witness |                **1** |                    **2**
(1 row)

-bash-4.2$ tail -f /var/log/repmgr.log
[2022-09-07 22:12:42] [INFO] witness node "wn01" (ID: 3) monitoring primary node "pg02" (ID: 2) in normal state
[2022-09-07 22:13:42] [INFO] witness node "wn01" (ID: 3) monitoring primary node "pg02" (ID: 2) in normal state
[2022-09-07 22:14:43] [INFO] witness node "wn01" (ID: 3) monitoring primary node "pg02" (ID: 2) in normal state

how did you create the witness? (step)