> > I have been getting the dreaded "unexpected EOF on client > > connection" in my system logs, but the surprising thing is that > > it comes from psql (I think). I am executing psql > > via a 'system' system call, and about 1 time out of 20 I get > > the "unexpected EO...
> client: Connection reset by peer > LOCATION: pq_recvbuf, pqcomm.c:678 > 2004-04-26 10:20:02 [24335] LOG: 08P01: unexpected EOF on client connection > LOCATION: SocketBackend, postgres.c:281[/color] This means the client is crashing or dropping the connection--you need to be look...
A Postgres database is hosted on a Gluster volume. The volume has been tuned for performance. Postgres operations throw an error that includes the string "ERROR: unexpected data beyond EOF in block". Here is an example of this type of error: Raw pg_restore: [archiver (db)] COPY failed ...
When we upgrade v8.0.0 to v10.0.0, I have a error log unexpected EOF on client connection with an open transaction with postgres for exec cmd docker logs -f xxxx. Not sure if it will affect the service?
Using default tag: latest Error response from daemon: Get "https://registry-1.docker.io/v2/": unexpected EOF docker version Client: Cloud integration: v1.0.29 Version: 20.10.22 API version: 1.41 Go version: go1.18.9 Git commit: 3a2c30b Built: Thu Dec 15 22:28:41 2022 OS/Arch: ...
Description Description When pushing a image to the registry, always get an upload error at around 60 seconds after the process begins, no matter the size of the current layer being uploaded, the error is always around 60 seconds in the ...
Docker fails at pulling the image with anunexpected EOFerror: PS C:\Dev> docker run hello-world Unable to find image 'hello-world:latest' locally C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: Get https://registry-1.docker.io/v2 /library/hello-world/...