From: | Johannes Mols <johannes(dot)mols(at)gmail(dot)com> |
---|---|
To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
Cc: | Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault |
Date: | 2020-04-08 13:56:48 |
Message-ID: | CAOiYe5sBb8U5HpTh5YnqiVNODGJw-bDT7LUyrUwjz4C5BY99aQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi Daniele,
That is strange. My configuration is that it is a remote Ubuntu machine and
I'm connecting over the regular port in pgAdmin.
My Python script is running on the same machine though, so it's just using
localhost as the connection.
Johannes
On Wed, Apr 8, 2020 at 3:52 PM Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
wrote:
> >> I have a PostgreSQL 10.12 server running on an Ubuntu 18.04 Server.
> Since
> >> today, I am suddenly getting errors when querying data from a Python
> script
> >> running on the same machine, and in some edge cases also in pgAdmin 4.
> >>
> >> In about 50% of the cases, my Python script will fail to return any data
> >> because the DB server closed the connection. I am using psycopg2 and it
> is
> >> giving me the following error:
> >>
> >> psycopg2.errors.AdminShutdown: terminating connection due to
> administrator
> >> command
> >> server closed the connection unexpectedly
> >> This probably means the server terminated abnormally
> >> before or while processing the request.
> >>
>
> On Thu, 9 Apr 2020 at 00:15, Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com> wrote:
> >
> > Unfortunately, there isn't enough information here for anybody to
> reproduce the issue.
> > Perhaps you can start by validating your own environment for any changes
> since the
> > database server was running fine for almost a month before you started
> seeing this
> > issue.
> >
> > For anybody to be of any help, they'll need complete steps to reproduce
> this issue,
> > and a core dump that carries enough debugging information to track the
> problem.
>
>
> Weirdly enough, we have received a handful of bug reports in the last
> 24 hours about unexpected disconnections:
>
> - https://github.com/psycopg/psycopg2/issues/1078
> - https://github.com/psycopg/psycopg2/issues/1079
>
> None of the OPs haven't specified their network configurations though.
> A similar report a few days ago
> (https://github.com/psycopg/psycopg2/issues/1066) had Azure to blame.
>
> -- Daniele
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-04-08 14:10:59 | Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault |
Previous Message | Daniele Varrazzo | 2020-04-08 13:52:36 | Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault |