Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: Re: Connection issue
From: Maximilian Tyrtania <maximilian.tyrtania@gmail.com>
In-Reply-To: <eac5c104-79e3-f5be-856c-2118e52d13d8@aklaver.com>
Date: Wed, 6 Feb 2019 17:30:31 +0100
Cc: Ricardo Martin Gomez <rimartingomez@hotmail.com>,
 pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC64CB98-C017-433B-A6BB-87876B912101@gmail.com>
References: <4558AEAB-975E-495D-9001-409CD5A9E84E@gmail.com>
 <715197e9-84a1-d975-c29b-a3f054478c02@aklaver.com>
 <9DA0BBAF-5E13-4D23-877B-A86BE1C149D1@gmail.com>
 <eac5c104-79e3-f5be-856c-2118e52d13d8@aklaver.com>
To: Adrian Klaver <adrian.klaver@aklaver.com>
Precedence: bulk

Hi again,


> On 6. Feb 2019, at 17:19, Adrian Klaver <adrian.klaver@aklaver.com> =
wrote:
>=20
> 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
>=20
> So from a previous post:
>=20
> > Have you recently updated any of the involved software?
>=20
> Well, sure, but after I saw I couldn't connect ...
>=20
> 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)
>=20
> 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".
>=20
> Well if you are running Windows --> Parallels --> OS X(Mac) --> Serve, =
you are effectively testing the Mac also.
>=20
> As to 'Connection reset by peer':
>=20
> A grep of the Postgres source find this:
>=20
> interfaces/libpq/win32.c
>=20
> * Contains table and functions for looking up win32 socket error
> * descriptions. But will/may contain other win32 helper functions
> * for libpq.
>=20
>=20
> WSAECONNRESET, "Connection reset by peer"
>=20
> Looking up WSAECONNRESET finds this:
>=20
> =
https://docs.microsoft.com/en-us/windows/desktop/WinSock/windows-sockets-e=
rror-codes-2
>=20
>=20
> WSAECONNRESET
> 10054
>=20
> 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=20=