Re: LOG: could not send data to client: Broken pipe - Mailing list pgsql-general

From Adrian Klaver
Subject Re: LOG: could not send data to client: Broken pipe
Date
Msg-id bdffb8df-cf37-eaec-f719-c4ea9f375126@aklaver.com
Whole thread Raw
In response to RE: LOG: could not send data to client: Broken pipe  (TALLURI Nareshkumar <nareshkumar.talluri@socgen.com>)
List pgsql-general
On 6/2/20 12:20 PM, TALLURI Nareshkumar wrote:
> Hello Adrian,
> 
> 
> What is the application stack?        -   I will check with Application team and get back to you.
> 
> When I see Windows and interruptions to Postgres I think anti-virus software. Is there any running on the client?
----yes , symantec
 

Probably should check if AV software is logging anything at the time of 
the broken pipes.

> 
> Are the client and server on the same network?  yes
> 
> Are the client/server separated by a building, country, etc?  same country , But different Datacenter
> 
> 
> Regards,
> Narresh
> 
> -----Original Message-----
> From: Adrian Klaver <adrian.klaver@aklaver.com>
> Sent: Wednesday, June 3, 2020 12:38 AM
> To: TALLURI Nareshkumar SgscGtsPasDre <nareshkumar.talluri@socgen.com>; pgsql-general@postgresql.org
> Subject: Re: LOG: could not send data to client: Broken pipe
> 
> On 6/2/20 11:18 AM, TALLURI Nareshkumar wrote:
>> Hello Adrian Klaver,
>>
>> Here is the answers
>>
>>
>> What version of JDBC?                 :     9.3-1104-jdbc41
>>
>> What is the application stack?            :    Java
> 
> That is the programming language. I was looking for the actual applications used.
> 
>>
>> Client OS?                    :    windows 2016
> 
> When I see Windows and interruptions to Postgres I think anti-virus software. Is there any running on the client?
> 
>>
>> What is the network distance between the client/application and the server?
> 
> I should have been more specific:
> 
> Are the client and server on the same network?
> 
> Are the client/server separated by a building, country, etc?
> 
>> Reply from 184.6.160.214: bytes=32 time=2ms TTL=57 Reply from
>> 184.6.160.214: bytes=32 time=2ms TTL=57 Reply from 184.6.160.214:
>> bytes=32 time=2ms TTL=57 Reply from 184.6.160.214: bytes=32 time=2ms
>> TTL=57
>>
>> Ping statistics for 184.6.160.214:
>>       Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate
>> round trip times in milli-seconds:
>>       Minimum = 2ms, Maximum = 2ms, Average = 2ms
>>
>>
>> Regards,
>> Narresh
>>
>>
>>
>>
>> -----Original Message-----
>> From: Adrian Klaver <adrian.klaver@aklaver.com>
>> Sent: Tuesday, June 2, 2020 7:50 PM
>> To: TALLURI Nareshkumar SgscGtsPasDre
>> <nareshkumar.talluri@socgen.com>; pgsql-general@postgresql.org
>> Subject: Re: LOG: could not send data to client: Broken pipe
>>
>> On 6/1/20 8:41 PM, TALLURI Nareshkumar wrote:
>>> Hello Postgres Support Team,
>>>
>>> I need your help to identify the issue and apply the fix for it.
>>>
>>> My client is running one query through Application and getting error
>>> like below.
>>>
>>> 11:20:46.298 [http-nio-8083-exec-7] ERROR
>>> c.s.s.g.a.alcor.pdi.dao.PdiDao
>>> - While getting pdi from 2019-12-21 to 2020-06-01: An I/O error
>>> occurred while sending to the backend.
>>>
>>> org.postgresql.util.PSQLException: An I/O error occurred while
>>> sending to the backend.
>>>
>>
>> Should have included in previous post:
>>
>> What version of JDBC?
>>
>> What is the application stack?
>>
>> Client OS?
>>
>> What is the network distance between the client/application and the server?
>>
>>
>> --
>> Adrian Klaver
>> adrian.klaver@aklaver.com
>>
> 
> 
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: raf
Date:
Subject: Re: Oracle vs. PostgreSQL - a comment
Next
From: "Andrus"
Date:
Subject: canceling statement due to conflict with recovery after pg_basebackup