Thread: PostgreSQL 13 - Logical Replication - ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF detected

Hello everyone,

I have a replication between PostgreSQL 12 to 13 in the production system. Using Ubuntu 18.04 LTS
We have this error today.
2023-05-18 18:34:04.374 WAT [117322] ERROR:  could not receive data from WAL stream: SSL SYSCALL error: EOF detected
2023-05-18 18:34:04.381 WAT [118393] LOG:  logical replication apply worker for subscription "inov_transactionnal_table_bertoua_sub_00" has started
2023-05-18 18:34:04.423 WAT [1039] LOG:  background worker "logical replication worker" (PID 117322) exited with exit code 1
2023-05-18 18:47:51.485 WAT [66836] postgres@inov_henrietfreres_v71_00 LOG:  could not receive data from client: Connection timed out.


Any idea how to solve this?
--
Jaurès FOUTE
At Thu, 18 May 2023 21:00:08 +0100, FOUTE K. Jaurès <jauresfoute@gmail.com> wrote in
> Hello everyone,
>
> I have a replication between PostgreSQL 12 to 13 in the production system.
> Using Ubuntu 18.04 LTS
> We have this error today.
>
>
>
> *2023-05-18 18:34:04.374 WAT [117322] ERROR:  could not receive data from
> WAL stream: SSL SYSCALL error: EOF detected
> 2023-05-18 18:34:04.381 WAT [118393] LOG:  logical replication apply worker for subscription
"inov_transactionnal_table_bertoua_sub_00"has started 
> 2023-05-18 18:34:04.423 WAT [1039] LOG:  background worker "logical replication worker" (PID 117322) exited with exit
code1 
> 2023-05-18 18:47:51.485 WAT [66836] postgres@inov_henrietfreres_v71_00 LOG:  could not receive data from client:
Connectiontimed out.* 
>
> *Any idea how to solve this?*

According to the message, the SSL-encrypted replication connection got
disconnected unexpectedly. I suppose it is due to the death of the
upstream server or some reasons outside of PostgreSQL. It seems like
the issue had been persisting for a few minutes after that. Other than
the server's death, I doubt some network hardware problems or changes
of firewall or networking setup of the OS. I think it would be good
idea to check for them first.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center





Le ven. 19 mai 2023 à 05:02, Kyotaro Horiguchi <horikyota.ntt@gmail.com> a écrit :
At Thu, 18 May 2023 21:00:08 +0100, FOUTE K. Jaurès <jauresfoute@gmail.com> wrote in
> Hello everyone,
>
> I have a replication between PostgreSQL 12 to 13 in the production system.
> Using Ubuntu 18.04 LTS
> We have this error today.
>
>
>
> *2023-05-18 18:34:04.374 WAT [117322] ERROR:  could not receive data from
> WAL stream: SSL SYSCALL error: EOF detected
> 2023-05-18 18:34:04.381 WAT [118393] LOG:  logical replication apply worker for subscription "inov_transactionnal_table_bertoua_sub_00" has started
> 2023-05-18 18:34:04.423 WAT [1039] LOG:  background worker "logical replication worker" (PID 117322) exited with exit code 1
> 2023-05-18 18:47:51.485 WAT [66836] postgres@inov_henrietfreres_v71_00 LOG:  could not receive data from client: Connection timed out.*
>
> *Any idea how to solve this?*

According to the message, the SSL-encrypted replication connection got
disconnected unexpectedly. I suppose it is due to the death of the
upstream server or some reasons outside of PostgreSQL. It seems like
the issue had been persisting for a few minutes after that. Other than
the server's death, I doubt some network hardware problems or changes
of firewall or networking setup of the OS. I think it would be good
idea to check for them first.
Thx for feedback. BTW I didn't have any network issues.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center


--
Jaurès FOUTE