On Fri, 5 Aug 2022 22:37:33 +0000 Paul-Andre Panon via Uyuni Users <users@lists.uyuni-project.org> wrote:
What role does lkv-srvapp39 serve? Is it your postgresql database server? That of a second Uyuni postgresql server you are trying to [..]
lkv-srvapp39 is running Uyuni AND the PostgreSQL server. So all communication is running on the same machine internally. Our DNS service is providing an A-record for lkv-srvapp39.lkvbay.net to the IP-address of the primary network interface. The server is multihomed with about 6 network adapters.
There could be a whole bunch of things that could be causing that: a) DNS resolution? Maybe the lkv-srvapp39 server doesn't have a proper DNS entry. Maybe the Uyuni server has the wrong DNS server configured for resolving that name. Can you use nslookup to resolve the name from the Uyuni app server?
What exactly do you mean with a proper DNS entry?
b) typo on the name in the configuration file? c) missing
Which configuration file?
domain name (not FQDN) and no DNS domain search configured in your resolver configuration? Or it's a different internal domain from your HUB server and there's no trust/forwarding setup for DNS between those domains? d) routing issue? e) host-based firewall on the (remote?) PG server not allowing connections on the TCP/5432 port? f) physical firewall or router ACLs preventing the connection?
Don't know if it helps but most of the Uyuni functions are running fine. Is it possible that updating repositories and salt clients works fine if the PostgreSQL server (on the same machine) cannot be accessed?
You're going to have to identify any other possibilities for your topology and then test all of them using other means (nslookup, ping, traceroute, psql, etc) to see what's not working.
As mentioned before: Anything is running on the same (virtual) machine. Regards, Tobias Crefeld.