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 1tKZzs-009W5x-9r for pgsql-admin@arkaria.postgresql.org; Mon, 09 Dec 2024 09:24:08 +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 1tKZzp-006AVh-Lc for pgsql-admin@arkaria.postgresql.org; Mon, 09 Dec 2024 09:24:06 +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 1tKZzp-006AVZ-4O for pgsql-admin@lists.postgresql.org; Mon, 09 Dec 2024 09:24:06 +0000 Received: from mail-qk1-x72c.google.com ([2607:f8b0:4864:20::72c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tKZzn-001qQF-LD for pgsql-admin@lists.postgresql.org; Mon, 09 Dec 2024 09:24:05 +0000 Received: by mail-qk1-x72c.google.com with SMTP id af79cd13be357-7b6c2bc1d21so150224185a.0 for ; Mon, 09 Dec 2024 01:24:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=opsveda.com; s=google; t=1733736242; x=1734341042; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=lvrASs/D3wGxkASuPKQwEv8q1CLiu2vyQCwiwCyfVXc=; b=VjdJGyFJ4EK0EUWpgRyWtueYXy0MVKA/vHttCbSpJDozkG1Y5JNsrf3pnTmCel7I3P o/m/55X/6d+LgbEhROmG7GLtdhIEDs7Q5b+XEqzSoCmml4HuzQrvZFimUvk6751q4YQL gW92ILGsFBklOaiXAltZ9KYyF4rKVRZzXGrNZnDpTejjJbztLCACcqLH4+qFAAi3wzGB +aXSsSfzUOC6w8RdawO1hNmAUuUW72gLhjgSHP2BP/AS+3co4Ert3IdKNnN+am7V69F5 IB8dL0wIWXRY8BfsN7JGKGC9w8Lsw88gBuOWT9+Z/GI9OILgLVkU+sOMeqYZkPDd9Cj0 UgPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733736242; x=1734341042; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=lvrASs/D3wGxkASuPKQwEv8q1CLiu2vyQCwiwCyfVXc=; b=ZyNyiQbK88K2ixvJZpj8B5rEHr5Xif1omX0DBPkcpzBRn67ClNzg1ch//TvqnHELLL H/aLQiBduCQYmQNIlPq9c4+9FTt+5k5a816L0tFwq7PsPrCmEDHDqtvnWj5gj2srN5qU PjDfhX1jkdF6poU5WBLr4x7giqWVP0YEJlBcOMiiyN40ryUcz9MGi/3UEALNiWNi11/M zit1AuvIfKcDY58y+t/M7op2cWhHcQRlj/2j+qAcExaB1hhmG2u7/HOt7sLot8aCPUyP 8+zzPhgl4dlRy2RjB0i/bBdkbAf7Qy4vdfnF+77Ydy/u7cjSYUa7eswp0WolQvzBRakA NvyA== X-Gm-Message-State: AOJu0Yy9YL3ovhWo2fPimSQXU9Fb886ZKQ/bOdEboWFDMmu7hct0wjlh 47OInWNXXNBsCWNSwGxdyloJurLtaf+os9j+6A0BQgZS/j/IGzfApxs0Qxl7b3l3Krgr19rWWJ0 eyN3ye8RYoBJ3xi2cSzxm3+EsJ8OO+nD1rkTpYwFwMsvcV4vlgG0= X-Gm-Gg: ASbGncs8RGiF1Bb3wLYW8vFwbgS3bIPfTALyeu5VNWZvd3DJZsxSZSAI9E3DCzOJbrI 2oo8DC/Ul9EPXKPl69+NBbrizcOs7gGPrLdLjjMKR3Icw6Lkg+iAzOGqJSGv2T9o= X-Google-Smtp-Source: AGHT+IFX57nKpyLJ7zcb7LnUVKS0h75BZU4ci86/WJVJ/mxrleLQwWMsyX9Dqz0jIGTEEtHusNMyHsNVoGZgdXIpX2c= X-Received: by 2002:a05:6870:ebca:b0:29e:5cb1:b148 with SMTP id 586e51a60fabf-29f731beaedmr6863383fac.6.1733729110796; Sun, 08 Dec 2024 23:25:10 -0800 (PST) MIME-Version: 1.0 From: Rijesh TP Date: Mon, 9 Dec 2024 12:54:58 +0530 Message-ID: Subject: SSL SYSCALL error during logical replication To: pgsql-admin@lists.postgresql.org Cc: Rajin Raj , Srikar Vankadaru Content-Type: multipart/alternative; boundary="000000000000c945e30628d14311" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c945e30628d14311 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Team, 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."* Logical replication had been working perfectly on version 15.8, and we successfully completed multiple systems on that version. However, after upgrading to PostgreSQL 15.10, this issue has arisen. We=E2=80=99ve tried adjusting various parameters but haven=E2=80=99t had an= y success. We have also tried disabling the SSL and selinux etc, but no luck, same error every time. Replication fails at some point without any additional errors, leading us to suspect a potential bug in logical replication for version 15.10. Has anyone else reported a similar issue, or is there a known fix for this? Please let us know if additional details are required. PG Version : postgresql 15.10 OS Details : CentOS 7 Thanks & Regards, Rijesh --000000000000c945e30628d14311 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,
We are encountering an issue with logical rep= lication on PostgreSQL version 15.10. The error message is as follows:
<= br>"ERROR: could not receive data from WAL stream: SSL SYSCALL erro= r: EOF detected
LOG: background worker "logical replication worker&= quot; (PID 3286) exited with exit code 1."


Logical replicat= ion had been working perfectly on version 15.8, and we successfully complet= ed multiple systems on that version. However, after upgrading to PostgreSQL= 15.10, this issue has arisen.
We=E2=80=99ve tried adjusting various par= ameters but haven=E2=80=99t had any success.
We have also tried disabli= ng the SSL and selinux etc, but no luck, same error every time.
Replicat= ion fails at some point without any additional errors, leading us to suspec= t a potential bug in logical replication for version 15.10.

Has anyo= ne else reported a similar issue, or is there a known fix for this? Please = let us know if additional details are required.

PG Version : postgre= sql 15.10
OS Details : CentOS 7



Thanks &=C2=A0Regards= ,
Rijesh
--000000000000c945e30628d14311--