Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tOa5R-007Jzj-DV for pgsql-admin@arkaria.postgresql.org; Fri, 20 Dec 2024 10:18:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tOa5O-008pQK-Px for pgsql-admin@arkaria.postgresql.org; Fri, 20 Dec 2024 10:18:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tOa5O-008pQC-BN for pgsql-admin@lists.postgresql.org; Fri, 20 Dec 2024 10:18:22 +0000 Received: from mail-oa1-x29.google.com ([2001:4860:4864:20::29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tOa5H-000jhP-8W for pgsql-admin@lists.postgresql.org; Fri, 20 Dec 2024 10:18:21 +0000 Received: by mail-oa1-x29.google.com with SMTP id 586e51a60fabf-2a3bf796cccso721178fac.1 for ; Fri, 20 Dec 2024 02:18:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=opsveda.com; s=google; t=1734689893; x=1735294693; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=m3I7zz/G+WFX2pA4wXveew2aLd6ZUYpC5KnJ5s86f+8=; b=xAuPTxM/J7lMirTBRYaAPSw50TW8k5m+iBHpI91zXZOOlBqnWpCrmIED9SF39lGE4w NNa7VlphycgF7k/D6yyJ8fQ8yhu2oFvmewvjm2REsD5+wbyYyvOEOPsgbyqCdop6cFkG aob22elbxMYmiwO2w8MRzzQW8iPBFrcsS5GIUiL+6dmPIfsKYaqZtuSXjmYVwwF2KiXl 3LRYKEjxBcs6Z1s6LA0JB9guKnpVkh8+qWL9Ww3xjSXRjIliMQWU7z2eZD4fpWMOEmNT ZwIVoe68WtAE0AUxDERnu4SLiwLNzAIeXRAcUbR0k3i9sDEk7T0dVc+dKZHqinau0EJd FBiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734689893; x=1735294693; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=m3I7zz/G+WFX2pA4wXveew2aLd6ZUYpC5KnJ5s86f+8=; b=eS8KWklM5IkZ0qPxRUMvjBPa80ab/idjP3NvbCJ8kG1TI3gS3dkc/oTntYo48WcJWU 6ThTFhk/6CJgePMp+GnFyOaE57zoMlgqoeK/l0ocAw9cbXp9sbR6xUAfvAWFXnsqlYcj fl9aWA0zg2d5gkb5p1+I5Oqq/YAiB0RRuDNNdFhtIbjqHEuBlDBpBZHgdTUDm8MrWgJF 6AR1jGtiy6famRWJWv2SLRrAqr+Hy1RFMvPBdAcAE4kckcQC9g/DGI24TEagaZGymCfe P8PKMydSqXvhRh/CYOqimTeYAGVxEGvhhCed0FTKJgeufEFnzX4OM455RLHbRL15x1Se k5GQ== X-Gm-Message-State: AOJu0YyB+/svG1BQR3/8D/1CqUT3nbX4YZ1PxiZjwQmdFlGfE2G4bSQM yjmnjJ/iGRALeYmZJgUM0Kn5Kk/zXesi7MOwdgMfpT6fUnv20TJKS9YzkbPA6o41nNL86TuW/uP PhJp8d+CONlEpzvLBaAehKJtCyrIQT+72w7uACg== X-Gm-Gg: ASbGncvWqq4gksbdfGa6lmg/4oHX9CsGIdPEoFB1w+IvnIFPKpFWXVuKLoJcAK14+3j M6eq1AiH9XPG1U+yqT0MQI1Mxx1WCFU/dq6NjiZE4KRfcSP3jm7hiksSPmDmihvaQaypt7A== X-Google-Smtp-Source: AGHT+IGN8AbzEfvCyrzfTKvUUF9azGbIZaVJqj0aQmCuSWUr+xaH6ejUsx67UzLMGlp8hGJWJKRlNMFY/76a/cIh4JA= X-Received: by 2002:a05:6870:5691:b0:29e:2d18:2718 with SMTP id 586e51a60fabf-2a7fb2f9e64mr1138948fac.28.1734689893573; Fri, 20 Dec 2024 02:18:13 -0800 (PST) MIME-Version: 1.0 References: <3910290.1733761359@sss.pgh.pa.us> In-Reply-To: <3910290.1733761359@sss.pgh.pa.us> From: Rijesh TP Date: Fri, 20 Dec 2024 15:48:02 +0530 Message-ID: Subject: Re: SSL SYSCALL error during logical replication To: Tom Lane Cc: pgsql-admin@lists.postgresql.org, Rajin Raj , Srikar Vankadaru Content-Type: multipart/alternative; boundary="000000000000e6ff570629b0f69d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e6ff570629b0f69d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=3Dreplicator 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=E2=80=AFPM Tom Lane wrote: > Rijesh TP 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 > --000000000000e6ff570629b0f69d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Tom,
Thanks for the reply.
On the so= urce DB,=20 we're seeing these messages coming up often, but there aren't any o= ther errors showing up.
All DB parameters including timeout we set to high, but no luck=C2=A0ye= t.
Pls advise on this

user=3Dreplicator DEBUG: =C2=A0failed to= increase restart lsn: proposed 13EB/B420DE18, after 13EB/B420DE18, current= candidate 13EB/B420DD70, current after 13EB/B420DD70, flushed up to 13EB/B= 420DBB0


Thanks &a= mp; Regards,
Rijesh

=C2=A0




On Mon, Dec 9, 2024 at 9:52=E2=80= =AFPM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Ri= jesh TP <rije= sh.tp@opsveda.com> writes:
> We are encountering an issue with logical replication on PostgreSQL ve= rsion
> 15.10. The error message is as follows:

> *"ERROR: could not receive data from WAL stream: SSL SYSCALL erro= r: 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.=C2=A0 Have you looked into that postmaster's log file to see what=
happened?

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 regards, tom lane
--000000000000e6ff570629b0f69d--