Any further tips/ troubleshooting needed for this issue? Please let me know.
Thanks, Sri. On Wed, May 27, 2026 at 8:14 PM Srinivas Kumar <[email protected]> wrote: > In our company all team members face this broken pipe , client side > disconnect while using DBeaver. Any fixes for it? As we have same tool > working fine for dev server. > > On Wed, 27 May 2026 at 7:49 PM, Roberto Mello <[email protected]> > wrote: > >> On Wed, May 27, 2026 at 4:19 PM Srinivas Kumar <[email protected]> >> wrote: >> >>> Hello Tomas, >>> >>> Thanks for reaching out! For more details, users connect directly to >>> PostgreSQL using the DBeaver tool. Please review the attached error >>> messages in the PostgreSQL server logs, and the timeout error on the >>> EDWDBPRDL01A server. We have another dev server in Windows, which works >>> absolutely fine without this issue, as you can review. Please let me know >>> if any more specific details are required. >>> >> >> From the logs you sent I don't see anything that jumps out. >> >> - 58 lines total >> - 6 connection authenticated >> - 6 connection authorized >> >> Only one problem: FATAL 08006 connection to client lost on PID 1994906 >> (pgAdmin -> EDW, 18:56:11). Preceded by LOG 08006 - could not send data to >> client: Broken pipe. pgAdmin dropped the TCP socket while the session was >> idle. Postgres detected it when it tried to write back. Client-side >> disconnect, not a server error. >> >> Everything else is normal: SETs, idle state transitions, and clean >> disconnections. No auth failures, no query errors, no locks, no timeouts >> recorded server-side. >> >> Roberto >> >
