From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Error: server closed the connection unexpectedly |
Date: | 2021-10-10 20:17:23 |
Message-ID: | ed3e5239-2312-80c3-b5cc-1e596a1ae9e6@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/10/21 13:06, Ron wrote:
> On 10/10/21 3:00 PM, Tom Lane wrote:
>> Ron <ronljohnsonjr(at)gmail(dot)com> writes:
>>> This is AWS RDS Postgresql. The db server log is accessed via a web
>>> interface, and is /the/ postgresql log just like you see in vanilla
>>> Postgresql.
>>> I've attached it. My attempt to connect happened some time between
>>> between
>>> 04:10:30 and 04:17:30.
>> Hm. Not much there. You might try turning on log_connections to be
>> sure,
>
> I'll do that.
>
>> but what this looks like is that the connection request never
>> got to the server. Maybe you've got some middleware involved, like
>> pgpool or some other connection pooler?
>
> If so, it must be something hidden by AWS, because I never installed it.
>
> The crazy thing is that coworkers with accounts on the same VM can
> connect to the instance just fine. (Yes, we use the exact same command
> to connect, as a test.)
Are the AWS security groups set up correctly.
See here:
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2021-10-10 21:26:07 | Re: Error: server closed the connection unexpectedly |
Previous Message | Adrian Klaver | 2021-10-10 20:12:03 | Re: Error: server closed the connection unexpectedly |