ClusterLabs / ClusterLabs/resource-agents
WARNING: Can't get <node-name> xlog location.
- Dominant language
- Shell
- Stars
- 519
- Forks
- 608
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
Hello,
I attempted to create an HA postgres cluster but the primary resource won't come to alive.
PostgreSQL version: 11.19
Pacemaker version: 2.1.4
OS Distribution: AlmaLinux 9.1
##############################
Cluster and Resource status:
* Resource Group: master-group:
* vip-master (ocf:heartbeat:IPaddr2): Stopped
* Resource Group: slave-group:
* vip-slave (ocf:heartbeat:IPaddr2): Stopped
Node Attributes:
* Node: 10.66.59.83:
* master-pgsql : -INFINITY
* pgsql-data-status : LATEST
* pgsql-status : HS:alone
* pgsql-xlog-loc : 0000000006000098
* Node: 10.66.59.84:
* master-pgsql : -INFINITY
* pgsql-master-baseline : 0000000004000098
* pgsql-status : HS:alone
* pgsql-xlog-loc : 0000000004000098
##############################
pacemaker.log is repeating below lines,
Mar 09 10:31:16 pgsql(pgsql)[3290789]: INFO: Master does not exist.
Mar 09 10:31:16 pgsql(pgsql)[3290789]: INFO: My data status=LATEST.
Mar 09 10:31:16 pgsql(pgsql)[3290789]: WARNING: Can't get node-1 xlog location.
Mar 09 10:31:16 pgsql(pgsql)[3290789]: WARNING: Can't get node-2 xlog location.
Mar 09 10:31:20 pgsql(pgsql)[3290995]: INFO: Master does not exist.
Mar 09 10:31:20 pgsql(pgsql)[3290995]: INFO: My data status=LATEST.
Mar 09 10:31:20 pgsql(pgsql)[3290995]: WARNING: Can't get node-1 xlog location.
Mar 09 10:31:20 pgsql(pgsql)[3290995]: WARNING: Can't get node-2 xlog location.
I'm sure that the xlog's location is correct when I created the resource.
Am I using the wrong packages?
Do you have any example commands to create this cluster?
Contributor guide
No contributing guide indexed for this repository
Research direction
The report names the PostgreSQL resource agent, Pacemaker logs, and the cluster and node-attribute status, but no source file or test. Start by reproducing the HA cluster setup with PostgreSQL 11.19 and Pacemaker 2.1.4, then trace the repeated xlog-location warnings and stopped resources. Done means the cause is identified and a verified fix or configuration resolution is recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, postgresql, shell
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100