RE: BUG #15078: Unable to receive data from WAL Stream Error

From: "Kolla, Mahesh" <Mahesh(dot)Kolla(at)transunion(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Eric Radman <ericshane(at)eradman(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: RE: BUG #15078: Unable to receive data from WAL Stream Error
Date: 2018-02-22 19:38:22
Message-ID: 78e189efca37446b98eaacf2399ff1c2@transunion.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello Tom,

We got information from network team saying that primary and standby are communicating through a switch ,there is no firewall at all

Please let me know why we are getting below associated LOGS saying invalid resource manager with the FATAL message Unable to receive data from WAL Stream Error as well. It looks like a bug

> sh: dev/null: No such file or directory
> sh: dev/null: No such file or directory < 2018-02-19 01:37:48.860 CST
> > LOG: invalid resource manager ID 48 at
> 15/2D69E848

Thank you
Mahesh Kolla

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, February 22, 2018 12:19 PM
To: Kolla, Mahesh <Mahesh(dot)Kolla(at)transunion(dot)com>
Cc: Eric Radman <ericshane(at)eradman(dot)com>; pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15078: Unable to receive data from WAL Stream Error

"Kolla, Mahesh" <Mahesh(dot)Kolla(at)transunion(dot)com> writes:
> Thank you for the response. Primary is accepting the ssl connections
> .Stand by is in sync with primary all the time but we receive FATALS
> sometimes 3 to 4 times a day which make us worry if having any data
> corruption

I doubt this is a PG bug; it sounds more like a networking problem.
Maybe there's a router or firewall in between that is timing out your connections too easily. If you can't adjust the network infrastructure, you could try enabling TCP keepalives (with a shorter repeat interval than the default) on the replication connections.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-02-22 20:58:01 BUG #15079: [54000] ERROR: total size of jsonb array elements exceeds the maximum of 268435455 bytes
Previous Message Magnus Hagander 2018-02-22 19:35:08 Re: BUG #15076: postmaster crashes unexpectedly when using up arrow key in psql command