Connection issue
For some reason I can't connect to my PG 10.6.1 Server (running on Ubuntu) from
my Windows installation (run via Parallels on my Mac), no matter what app I use
(tried psql, PGAdmin and my own app).
When trying to connect from PGAdmin 4 the server logs say:
2019-02-05 10:34:30.558 CET [31051] [unbekannt]@[unbekannt] LOG: 0:
Verbindung empfangen: Host=ip5b4054ce.dynamic.kabel-deutschland.de Port=50262
2019-02-05 10:34:30.558 CET [31051] [unbekannt]@[unbekannt] ORT:
BackendInitialize, postmaster.c:4249
2019-02-05 10:34:30.648 CET [31051] [unbekannt]@[unbekannt] LOG: 08006: konnte
Daten vom Client nicht empfangen: Connection reset by peer
2019-02-05 10:34:30.648 CET [31051] [unbekannt]@[unbekannt] ORT: pq_recvbuf,
pqcomm.c:978
("konnte Daten vom Client nicht empfangen" means "couldn't receive data from
client")
PGAdmin says the usual " Unable to connect to server:..."
No issue connecting from the Mac.
I see in the logfile that other windows users did connect successfully from
their windows boxes so I am ready to believe that maybe my Parallels somehow
disconnects the connection quickly or something.
Another strange thing is that if I try to connect from my Xojo app (which uses
libpq internally) it says:SSL error: unknown protocol. I had no issue
connecting last week from that installation so I am at my wits end...
Tia,
Max
Re: Connection issue
Hi,
> On 5. Feb 2019, at 15:57, Adrian Klaver wrote:
>
> On 2/5/19 1:48 AM, Maximilian Tyrtania wrote:
>> For some reason I can't connect to my PG 10.6.1 Server (running on Ubuntu)
>> from my Windows installation (run via Parallels on my Mac), no matter what
>> app I use (tried psql, PGAdmin and my own app).
>
> Has it ever connected?
Yes, it connected without issues last week.
> Have you recently updated any of the involved software?
Well, sure, but after I saw I couldn't connect I downloaded the current version
of PGAdmin and psql and couldn't connect with them either.
> More below.
>
>> When trying to connect from PGAdmin 4 the server logs say:
>> 2019-02-05 10:34:30.558 CET [31051] [unbekannt]@[unbekannt] LOG: 0:
>> Verbindung empfangen: Host=ip5b4054ce.dynamic.kabel-deutschland.de Port=50262
>> 2019-02-05 10:34:30.558 CET [31051] [unbekannt]@[unbekannt] ORT:
>> BackendInitialize, postmaster.c:4249
>> 2019-02-05 10:34:30.648 CET [31051] [unbekannt]@[unbekannt] LOG: 08006:
>> konnte Daten vom Client nicht empfangen: Connection reset by peer
>> 2019-02-05 10:34:30.648 CET [31051] [unbekannt]@[unbekannt] ORT:
>> pq_recvbuf, pqcomm.c:978
>> ("konnte Daten vom Client nicht empfangen" means "couldn't receive data from
>> client")
>> PGAdmin says the usual " Unable to connect to server:..."
>> No issue connecting from the Mac.
>> I see in the logfile that other windows users did connect successfully from
>> their windows boxes so I am ready to believe that maybe my Parallels somehow
>> disconnects the connection quickly or something.
>> Another strange thing is that if I try to connect from my Xojo app (which
>> uses libpq internally) it says:SSL error: unknown protocol. I had no issue
>> connecting last week from that installation so I am at my wits end...
>
> Where is the Xojo app running?
>
> Is the pg_hba.conf on the server set up to allow connections from the client
> machines?
Yes. Also the errormessage wouldn't be "Connection reset by peer" if it was a
pga_hba.conf issue, would it? And anyway, I can connect just fine from my Mac
with the same credentials. I wonder if this is maybe some Parallels issue.
Thanks,
Max
Re: Connection issue
Well, the problem being a Parallels issue is just a wild theory of mine, it could well be something else. Honstly I don't recall updating anything in that area. As Mr. Gomez suggested I tried to ping - worked telnet - did not work (infact I couldn't telnet anywhere) tracert - worked from my windows 10 box (didn't bother to check on my Mac as I have noc issues there). Still curious as to why the server would say "Connection reset by peer". Thanks, Max
Re: Connection issue
Hi again, > On 6. Feb 2019, at 17:19, Adrian Klaver wrote: > > On 2/6/19 7:18 AM, Maximilian Tyrtania wrote: >> Well, the problem being a Parallels issue is just a wild theory of mine, it >> could well be something else. Honstly I don't recall updating anything in >> that area. As Mr. Gomez suggested I tried to > > So from a previous post: > > > Have you recently updated any of the involved software? > > Well, sure, but after I saw I couldn't connect ... > > So what happened in the interval between the time you could connect and the > time you could not? I did update parts of my app (including the plugin which in turn encapsulates libpq). I did not update my parallels installation, as far as I remember. Sorry if I was unclear about that. >> ping - worked >> telnet - did not work (infact I couldn't telnet anywhere) > > In my experience telnet is generally disabled these days. I had to enable it on my Windows box, if that's what you mean. The "telnet" command works by itself, but I didnt receive anything when trying to telnet to some other machine. >> tracert - worked >> from my windows 10 box (didn't bother to check on my Mac as I have noc >> issues there). Still curious as to why the server would say "Connection >> reset by peer". > > Well if you are running Windows --> Parallels --> OS X(Mac) --> Serve, you > are effectively testing the Mac also. > > As to 'Connection reset by peer': > > A grep of the Postgres source find this: > > interfaces/libpq/win32.c > > * Contains table and functions for looking up win32 socket error > * descriptions. But will/may contain other win32 helper functions > * for libpq. > > > WSAECONNRESET, "Connection reset by peer" > > Looking up WSAECONNRESET finds this: > > https://docs.microsoft.com/en-us/windows/desktop/WinSock/windows-sockets-error-codes-2 > > > WSAECONNRESET > 10054 > > Connection reset by peer. >An existing connection was forcibly closed by the remote host. This > normally results if the peer application on the remote host is suddenly > stopped, the host is rebooted, the host or remote network interface is > disabled, or the remote host uses a hard close (see setsockopt for more > information on the SO_LINGER option on the remote socket). This error may > also result if a connection was broken due to keep-alive activity detecting a > failure while one or more operations are in progress. Operations that were in > progress fail with WSAENETRESET. Subsequent operations fail with > WSAECONNRESET. Ah, thanks for digging that up. Hmm, sounds as if something is definetly wrong on my windows box. I'll try contacting the Parallels support guys. Thanks again, Max
Re: Connection issue
Just for the record, updating to Mac OS 10.14.3 resolved the issue. Thanks, Max
