From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | "Javali, Pramod" <Pramod(dot)Javali1(at)t-mobile(dot)com> |
Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Unable to connect to server |
Date: | 2024-04-29 15:26:07 |
Message-ID: | CAMkU=1z2vkZ4gWMd_U+Vt8AWKGHnGDR8LV2=0bSd3d0DYG59OA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
This is unlikely to be a bug, it seems like an admin issue.
When I've seen this "server closed the connection unexpectedly" immediately
upon connection, it is usually because a port forwarder has accepted the
connection and tried to pass it on to the real server, but the forwarder
got a connection refused error. As it already accepted the connection, it
can't pass the "refused" back to the client so instead just closes it
without comment, which is unexpected.
If that is what is happening, you will not find any direct log messages in
the PostgreSQL log about it, as no connection was ever established and so
there is nothing to log. But if something else is going on, you might get
log messages so check for them.
Make sure that the PostgreSQL server is actually running, is listening on
the right port and the right network interface, and that any port
forwarder or firewall is configured correctly.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-04-29 17:32:17 | Re: edb installation failed for pgadmin when username is Chinese under c;\user #7432 |
Previous Message | Tom Lane | 2024-04-29 14:28:42 | Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize |