Re: How to debug incomplete message on postgres 12.3 docker
От | Dave Cramer |
---|---|
Тема | Re: How to debug incomplete message on postgres 12.3 docker |
Дата | |
Msg-id | CADK3HHLZ-9wLcCchn-2p3yXsusE2iQ0Yz5dr5eQLcabMV+kDbg@mail.gmail.com обсуждение исходный текст |
Ответ на | How to debug incomplete message on postgres 12.3 docker (R Batchen <batchenr@gmail.com>) |
Список | pgsql-general |
Dave Cramer
www.postgres.rocks
On Sun, 16 Jan 2022 at 10:13, R Batchen <batchenr@gmail.com> wrote:
Hello,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?i want to see when and who did the translation and what is the incomplete query ? because i did approached guacamole mailing list and they said my DB is closing connection in the middle of the transactionand its psql issue and i am not able to debug it because i only have this incomlit msg.Is there a way to catch this transaction?full logs :postgres_gqm_1 | 2022-01-13T19:32:24.187916615Z 2022-01-13 19:32:24.187 UTC [4394] LOG: incomplete message from client guacamole_1 | 2022-01-13T19:32:24.214231454Z 19:32:24.214 [http-nio-8080-exec-6] ERROR o.a.g.rest.RESTExceptionMapper - Unexpected internal error: guacamole_1 | 2022-01-13T19:32:24.214398980Z ### Error rolling back transaction. Cause: org.postgresql.util.PSQLException: This connection has been closed. guacamole_1 | 2022-01-13T19:32:24.214445260Z ### Cause: org.postgresql.util.PSQLException: This connection has been closed.
docker file :postgres_gqm:image: postgres:12.3 environment: PGDATA: /var/lib/postgresql/data/guacamole POSTGRES_DB: db POSTGRES_PASSWORD: XXX POSTGRES_USER: user restart: always volumes: - ./init:/docker-entrypoint-initdb.d:ro - ./data:/var/lib/postgresql/data:rw logging: driver: "json-file" options: max-size: "750m"
My guess is that the container dropped the connection somehow. Either network error or application error. I would look at the logs on the container.
There is no way to debug this on the postgres side (that I am aware of)
Dave
В списке pgsql-general по дате отправления: