From: | Rijesh TP <rijesh(dot)tp(at)opsveda(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org, Rajin Raj <rajin(dot)raj(at)opsveda(dot)com>, Srikar Vankadaru <srikar(at)opsveda(dot)com> |
Subject: | Re: SSL SYSCALL error during logical replication |
Date: | 2024-12-20 10:18:02 |
Message-ID: | CAN1ptccjjJ=D1ih2YxxKT-iTANKvij9dX7gBUuL87me+5voJ5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Tom,
Thanks for the reply.
On the source DB, we're seeing these messages coming up often, but there
aren't any other errors showing up.
All DB parameters including timeout we set to high, but no luck yet.
Pls advise on this
*user=replicator DEBUG: failed to increase restart lsn: proposed
13EB/B420DE18, after 13EB/B420DE18, current candidate 13EB/B420DD70,
current after 13EB/B420DD70, flushed up to 13EB/B420DBB0*
Thanks & Regards,
Rijesh
On Mon, Dec 9, 2024 at 9:52 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Rijesh TP <rijesh(dot)tp(at)opsveda(dot)com> writes:
> > We are encountering an issue with logical replication on PostgreSQL
> version
> > 15.10. The error message is as follows:
>
> > *"ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF
> > detectedLOG: background worker "logical replication worker" (PID 3286)
> > exited with exit code 1."*
>
> This seems to be a symptom of something going wrong on the sending
> side. Have you looked into that postmaster's log file to see what
> happened?
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | SOzcn | 2024-12-20 12:23:34 | Troubleshooting - PostgreSQL Session CPU Analyze |
Previous Message | Fabrice Chapuis | 2024-12-20 10:02:58 | barman partial duplicate file |