Horton

Thread

  1. DBeaver Experiencing timeouts while connecting to New Linux PostgreSql server

    Srinivas Kumar <srinivasnerusu@gmail.com> — 2026-05-27T20:27:19Z

    Hello,

My company has a new Linux production server of Postgresql 18. While
connecting to it in DBeaver, users are experiencing timeouts with broken
pipe
errors in logs. It connects randomly, 1 in every 3-4 attempts. Since this is
new servers in high available fashion with another standby server, there is
very little traffic and max connections are set to 300. How do we find RCA
for
this? Let me know if any additional details are required. I have checked all
security information and telnet, and it works just fine in CMD or a
terminal.

Looking forward to hearing from you.

Regards,
Sri.

  2. Re: DBeaver Experiencing timeouts while connecting to New Linux PostgreSql server

    Tomas Vondra <tomas@vondra.me> — 2026-05-27T21:37:32Z

    On 5/27/26 22:27, Srinivas Kumar wrote:
> Hello,
> 
> My company has a new Linux production server of Postgresql 18. While
> connecting to it in DBeaver, users are experiencing timeouts with broken
> pipe
> errors in logs. It connects randomly, 1 in every 3-4 attempts. Since this is
> new servers in high available fashion with another standby server, there is
> very little traffic and max connections are set to 300. How do we find
> RCA for
> this? Let me know if any additional details are required. I have checked all
> security information and telnet, and it works just fine in CMD or a
> terminal.
> 
> Looking forward to hearing from you.
> 

There not much information, so it's hard to give you good advice. We
don't even know how the users connect - is it directly or through a
pool/proxy of some sorts, or what? What logs have messages about broken
pipes - is that the Postgres server log or some other log?

You'll have to do the usual thing people do during RCA analysis, i.e. go
step by step over all the components on the connection (between the
client and the server), figure out where exactly it fails and why.

My guess is something is dropping the connection for whatever reason
(might be a proxy, might be a VPN, ... who knows?).


regards

-- 
Tomas Vondra

  3. Re: DBeaver Experiencing timeouts while connecting to New Linux PostgreSql server

    Srinivas Kumar <srinivasnerusu@gmail.com> — 2026-05-27T22:18:34Z

    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.

Thanks,
Sri.

On Wed, May 27, 2026 at 5:37 PM Tomas Vondra <tomas@vondra.me> wrote:

> On 5/27/26 22:27, Srinivas Kumar wrote:
> > Hello,
> >
> > My company has a new Linux production server of Postgresql 18. While
> > connecting to it in DBeaver, users are experiencing timeouts with broken
> > pipe
> > errors in logs. It connects randomly, 1 in every 3-4 attempts. Since
> this is
> > new servers in high available fashion with another standby server, there
> is
> > very little traffic and max connections are set to 300. How do we find
> > RCA for
> > this? Let me know if any additional details are required. I have checked
> all
> > security information and telnet, and it works just fine in CMD or a
> > terminal.
> >
> > Looking forward to hearing from you.
> >
>
> There not much information, so it's hard to give you good advice. We
> don't even know how the users connect - is it directly or through a
> pool/proxy of some sorts, or what? What logs have messages about broken
> pipes - is that the Postgres server log or some other log?
>
> You'll have to do the usual thing people do during RCA analysis, i.e. go
> step by step over all the components on the connection (between the
> client and the server), figure out where exactly it fails and why.
>
> My guess is something is dropping the connection for whatever reason
> (might be a proxy, might be a VPN, ... who knows?).
>
>
> regards
>
> --
> Tomas Vondra
>
>

  4. Re: DBeaver Experiencing timeouts while connecting to New Linux PostgreSql server

    Roberto Mello <roberto.mello@gmail.com> — 2026-05-27T23:49:14Z

    On Wed, May 27, 2026 at 4:19 PM Srinivas Kumar <srinivasnerusu@gmail.com>
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

  5. Re: DBeaver Experiencing timeouts while connecting to New Linux PostgreSql server

    Srinivas Kumar <srinivasnerusu@gmail.com> — 2026-05-28T00:14:19Z

    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 <roberto.mello@gmail.com>
wrote:

> On Wed, May 27, 2026 at 4:19 PM Srinivas Kumar <srinivasnerusu@gmail.com>
> 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
>