#1039 closed bug (wontfix)
PostGIS: unclear error message connecting to a wrong port
| Reported by: | msieczka | Owned by: | nobody |
|---|---|---|---|
| Priority: | minor: annoyance | Milestone: | |
| Component: | Data Provider | Version: | Trunk |
| Keywords: | Cc: | ||
| Must Fix for Release: | No | Platform: | All |
| Platform Version: | Awaiting user input: | no |
Description
When trying to connect to a port Postgres does not work on a cryptic "Extended error information" is given:
Connection failed - Check settings and try again. Extended error information: expected authentication request from server, but received S
Change History (4)
follow-up: 2 comment:1 by , 16 years ago
| Awaiting user input: | set |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
comment:2 by , 16 years ago
| Platform: | Debian → All |
|---|
Replying to jef:
Does the error message get truncated like that?
Exactly. All I get is:
Connection failed - Check settings and try again. Extended error information: expected authentication request from server, but received S
It was SSH port I tried to connect to by mistake.
I checked with PgAdmin. It displays same cryptic message. Not a QGIS issue it seems. Sorry for the fuss.
BTW - localised messages are garbled when they contain non-ASCII chars. Eg. in PL UTF8 locale I get:
Connection failed - Check settings and try again. Extended error information: could not connect to server: Przekroczony czas oczekiwania na poÅÄ czenie Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 22?
instead of:
Connection failed - Check settings and try again. Extended error information: could not connect to server: Przekroczony czas oczekiwania na połączenie Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 22?
Note:
See TracTickets
for help on using tickets.
Does the error message get truncated like that? I get
could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "192.168.49.12" and accepting TCP/IP connections on port 5433?which seems pretty clear. But I guess in your case there is something listing on the port you try to connect which even supports SSL as I get
when connecting a SMTP port w/o SSL.
Anyway, those error messages are returned by the postgres client library and passed on to the user as that is all we known and therefore probably the best we can do.