Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

crosscheck / matrix issue with non default pg port #790

Open
seadba opened this issue Jan 17, 2023 · 4 comments
Open

crosscheck / matrix issue with non default pg port #790

seadba opened this issue Jan 17, 2023 · 4 comments

Comments

@seadba
Copy link

seadba commented Jan 17, 2023

i have a v11 cluster on a non-default port 5443 - i have passwordless authentication set up and repgmr config works - nodes are registered and standby cloned and recovering - however if i run crosscheck or matrix i get the following errors
"could not connect to server: Connection refused
Is the server running on host "10.99.100.9" and accepting
TCP/IP connections on port 5432?"

  • node "10.99.100.9" (ID: 2) is registered as an active standby but is unreachable

conninfo on both servers

conninfo='host=10.99.100.9 port=5443 user=repmgr dbname=repmgr connect_timeout=2'

i cant figure out where the default 5432 is derived from - cluster show works fine from either node - however the port is not in repmgr.nodes

conninfo | host=10.99.100.10 user=repmgr dbname=repmgr connect_timeout=
2

any idea? thanks

@seadba
Copy link
Author

seadba commented Jan 17, 2023

other repmgr commands recognize the port

$ repmgr -f /etc/repmgr/11/repmgr.conf standby unregister
INFO: connecting to local standby
DEBUG: connecting to: "user=repmgr connect_timeout=2 dbname=repmgr host=10.99.100.9 port=5443 fallback_application_name=repmgr options=-csearch_path="
INFO: connecting to primary database
DEBUG: connecting to: "user=repmgr connect_timeout=2 dbname=repmgr host=10.99.100.10 fallback_application_name=repmgr options=-csearch_path="
NOTICE: unregistering node 2
INFO: standby unregistration complete

@seadba
Copy link
Author

seadba commented Jan 18, 2023

i switched to default 5432 and that seems to work - will test again with non-default port

@JP95Git
Copy link

JP95Git commented Apr 23, 2024

Possible related: #852

@Shagrat2
Copy link

I have same problem
2024-08-30_15-16-40 (2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants