Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Mariane Kiesewetter <mskiesewetter@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Disconnection errors
Date: Sun, 7 Feb 2021 22:36:40 +0100
Message-Id: <0FA3B661-B8EC-4C3A-94BD-9290EEF07BAB@gmail.com>
References: <fe8ab49e827a9e18a2ec34fadc296a3ba2ac5825.camel@cybertec.at>
Cc: S Bob <sbob@quadratum-braccas.com>, pgsql-admin@lists.postgresql.org
In-Reply-To: <fe8ab49e827a9e18a2ec34fadc296a3ba2ac5825.camel@cybertec.at>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Precedence: bulk

Hi
I have seen such messages when connections were dropped by the firewall afte=
r a certain time. I can=E2=80=99t remember the setting but will check if I c=
an find it tomorrow if you still need the info.=20

Regards
Mariane

> On 5 Feb 2021, at 14:19, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>=20
> =EF=BB=BFOn Thu, 2021-02-04 at 17:12 -0700, S Bob wrote:
>> I see lots of errors like this in the log:
>>=20
>> 2021-02-04 23:58:50.135 UTC [32591] ERROR:  canceling statement due to us=
er request
>> 2021-02-04 23:58:50.135 UTC [32591] STATEMENT:
>> 2021-02-04 23:58:50.135 UTC [32591] LOG:  could not send data to client: B=
roken pipe
>> 2021-02-04 23:58:50.135 UTC [32591] FATAL:  connection to client lost
>>=20
>> Is this due to the end user or app disconnecting? Are there other areas
>> / details I should be looking at to debug?
>=20
> That looks like the client sent a cancel request and then terminated
> without closing the database connection.
>=20
> What seems weird is the empty STATEMENT.
>=20
> Yours,
> Laurenz Albe
> --=20
> Cybertec | https://www.cybertec-postgresql.com
>=20
>=20
>=20