This is a very open ended issue :)
Ideally if you could confirm that
1) were you able to connect locally on the machine via psql on loopback (localhost) if it was allowed?
2) did logs emit any messages when trying to connect to the server?
3) if you have admin access to server, can you look at dmesg -a output on the reboot. If you mention you had issues with connecting even after restarting postgresql server, but it was fine after a reboot maybe the network interface had some issues. Do you see packet loss on the interface you are connecting to?
4) are there any monitoring enabled or replication enabled for this server ? Were they active or broken while the time you had issues connecting to the server?
5) are you connecting to the server directly or via pgbouncer or other layers ?
What version of postgresql
What client ( from my exp old npgsql clients had some bugs )
Where is it running? Cloud vm, docker ?
Thanks,
Vijay
On Fri, Apr 30, 2021, 1:19 AM Henry Francisco Garcia Cortez <garcortez@xxxxxxxxx> wrote:
Hi community greetings for everyone this morning I couldn't connect to postgresql but the daemon of postgresql was running, so I restarted the daemon of postgresql what happened nothing, so I decided to reboot server and while server was starting it showed a message a top job is running for postgresql Cluster after that I could connect to postgresql, I want to know some idea why couldn't I connect to postgresql? and I want some advices for avoiding that situation again
--Ing. Henry G. Cortez
