Re: How to debug incomplete message on postgres 12.3 docker

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: R Batchen <batchenr(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: How to debug incomplete message on postgres 12.3 docker
Date: 2022-01-16 17:04:37
Message-ID: 3706226.1642352677@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

R Batchen <batchenr(at)gmail(dot)com> writes:
> I hope i reached the right mailing list, i have psql 12.3 container that is
> the db of apache guacamole container is connected to,
> the apache guacamole stopped working and i started to get this message on
> the postgres:

> LOG: incomplete message from client

> How can I debug it?

This message indicates that the server collected a message header
(length word) from the communication channel, but then detected EOF
while trying to read that number of bytes. The two most plausible
explanations for that are (1) some external force closed the network
connection or (2) the client sent a invalid (far too large) length
word. But to believe (2) you'd also have to believe that the client
gave up and closed the connection before sending the number of bytes
the server thought it had promised. That could happen if the client
thought the command had timed out, but I'd expect it to log something
about a timeout if it had.

In short, I think something at the kernel or container level is
closing the connection under you. You need to be looking into those
system-level logs, as neither the postgres nor client logs would
have any evidence of the primary cause.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2022-01-16 17:05:47 Re: How to debug incomplete message on postgres 12.3 docker
Previous Message Dave Cramer 2022-01-16 16:16:12 Re: How to debug incomplete message on postgres 12.3 docker