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 1sW1Oj-00CosO-LI for pgsql-admin@arkaria.postgresql.org; Mon, 22 Jul 2024 22:20:49 +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 1sW1Oh-007TCv-GK for pgsql-admin@arkaria.postgresql.org; Mon, 22 Jul 2024 22:20:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sW1Oh-007TCm-4w for pgsql-admin@lists.postgresql.org; Mon, 22 Jul 2024 22:20:47 +0000 Received: from mail-cy.bbox.fr ([194.158.98.48]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sW1Oe-000vy9-Cr for pgsql-admin@lists.postgresql.org; Mon, 22 Jul 2024 22:20:45 +0000 Received: from mail.jpp.fr (unknown [176.187.84.182]) by mail-cy.bbox.fr (Postfix) with ESMTP id 7346F33; Tue, 23 Jul 2024 00:20:41 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 mail-cy.bbox.fr 7346F33 Received: from localhost (localhost [127.0.0.1]) by mail.jpp.fr (Postfix) with ESMTP id 3B6F6C0047; Tue, 23 Jul 2024 00:20:41 +0200 (CEST) Received: from mail.jpp.fr ([127.0.0.1]) by localhost (mail.jpp.fr [127.0.0.1]) (amavis, port 10032) with ESMTP id 0X5Sen7uzqvt; Tue, 23 Jul 2024 00:20:41 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.jpp.fr (Postfix) with ESMTP id 1DB08C0051; Tue, 23 Jul 2024 00:20:41 +0200 (CEST) X-Virus-Scanned: amavis at jpp.fr Received: from mail.jpp.fr ([127.0.0.1]) by localhost (mail.jpp.fr [127.0.0.1]) (amavis, port 10026) with ESMTP id scaKikuH1sNW; Tue, 23 Jul 2024 00:20:41 +0200 (CEST) Received: from mail.jpp.fr (localhost [127.0.0.1]) by mail.jpp.fr (Postfix) with ESMTP id EE9FBC0047; Tue, 23 Jul 2024 00:20:40 +0200 (CEST) Date: Tue, 23 Jul 2024 00:20:40 +0200 (CEST) From: Jean-Paul POZZI To: vrms Cc: pgsql-admin Message-ID: <1070044209.191.1721686840805.JavaMail.zextras@jpp.fr> In-Reply-To: <0322e728-fe36-45a4-9667-299246028db8@netcologne.de> References: <0322e728-fe36-45a4-9667-299246028db8@netcologne.de> Subject: RE: WAL file corruption on standby PostgreSQL MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_d66191c9-4e20-4eec-80ab-e820421c9505" X-Originating-IP: [192.168.2.8] X-Mailer: Carbonio 24.5.0_ZEXTRAS_202405 (CarbonioWebClient - Firefox 128.0 (Linux)/24.5.0_ZEXTRAS_202405 carbonio 20240517-1011 FOSS) Thread-Topic: WAL file corruption on standby PostgreSQL Thread-Index: H1FaC9HB3EjnLWQX8JAsM+5ZNcaNsQ== X-VADE-SPAMSTATE: clean X-VADE-SPAMSCORE: 0 X-VADE-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeeftddrheekgddutdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemuceuqfgfjgfifgfgufdpucfqfgfvpdcuggftfghnshhusghstghrihgsvgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvvefkjghfufggtghiofhtsegrtdgtreertdejnecuhfhrohhmpeflvggrnhdqrfgruhhlucfrqfgkkgfkuceojhhprdhpohiiiihisehiiiiiohhprdhnvghtqeenucggtffrrghtthgvrhhnpeetgeetteeuuefhjeffieevieeiffefuefhtefhtdehheekueejgfelvdefffelveenucfkphepudejiedrudekjedrkeegrddukedvpdduledvrdduieekrddvrdeknecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepudejiedrudekjedrkeegrddukedvpdhhvghlohepmhgrihhlrdhjphhprdhfrhdpmhgrihhlfhhrohhmpehjphdrphhoiiiiihesihiiiihophdrnhgvthdpnhgspghrtghpthhtohepvddprhgtphhtthhopehpghhsqhhlqdgrughmihhnsehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrghdprhgtphhtthhopehvrhhmshesnhgvthgtohhlohhgnhgvrdguvg List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=_d66191c9-4e20-4eec-80ab-e820421c9505 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, Some traces in Postgres or system logs ? De: "vrms" =C3=80: "undefined" Envoy=C3=A9: lundi 22 juillet 2024 21:26 Objet: Re: WAL file corruption on standby PostgreSQL On 7/22/24 8:42 PM, Muhammad Ikram wrote: >> Also try to see what caused corruption of WAL archives. out of curiosity ... any hint in how to approach this? On 7/22/24 8:42 PM, Muhammad Ikram wrote: Hi Wasim, IMO, you will have to rebuild the standby server by taking base backup from= Primary and copying it to standby, restart standby. Also try to see what c= aused corruption of WAL archives. Regards Muhammad Ikram On Mon, Jul 22, 2024 at 11:26=E2=80=AFPM Wasim Devale = wrote: Hi All 2024-07-22 11:15:10 PDT [1723]: [7028-1] user=3D,db=3D,app=3D,client=3D LOG= :=C2=A0 restored log file "000000010000170900000081" from archive 2024-07-22 11:15:10 PDT [1723]: [7029-1] user=3D,db=3D,app=3D,client=3D LOG= :=C2=A0 invalid resource manager ID 128 at 1709/8183BFA8 2024-07-22 11:15:10 PDT [1723]: [7030-1] user=3D,db=3D,app=3D,client=3D LOG= :=C2=A0 invalid resource manager ID 128 at 1709/8183BFA8 I got this error and the replication has stopped. Please suggest about=C2= =A0invalid resource manager ID. Thanks, Wasim -- Muhammad Ikram --=_d66191c9-4e20-4eec-80ab-e820421c9505 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hello,

 

Some traces in Postgres or system logs ?

 



De: "vrms" <vrms@netcologne.de>= ;
=C3=80: "undefined" <pgsql-admin@lists.postgresql= .org>
Envoy=C3=A9: lundi 22 juillet 2024 21:26
= Objet: Re: WAL file corruption on standby PostgreSQL
<= br>On 7/22/24 8:42 PM, Muhammad Ikram wrote:

>> Also try to se= e what caused corruption of WAL archives.

out of curiosity ... any h= int in how to approach this?



On 7/22/24 8:42 PM, Muhammad Ikram wrote:
Hi Wasim,
 
IMO, you will have to rebuild the standby server by taking base backup= from Primary and copying it to standby, restart standby. Also try to see w= hat caused corruption of WAL archives.
 
Regards
Muhammad Ikram
 

On Mon, Jul 22, 2024 at 11:26=E2=80= =AFPM Wasim Devale <wasimd60@gmail.com> wrote:<= /div>
Hi All
 
2024-07-22 11:15:10 PDT [1723]: [7028-1] user=3D,db= =3D,app=3D,client=3D LOG:  restored log file "000000010000170900000081= " from archive
2024-07-22 11:15:10 PDT [1723]: [7029-1] user=3D,db=3D,ap= p=3D,client=3D LOG:  invalid resource manager ID 128 at 1709/8183BFA8<= br>2024-07-22 11:15:10 PDT [1723]: [7030-1] user=3D,db=3D,app=3D,client=3D = LOG:  invalid resource manager ID 128 at 1709/8183BFA8
 
 
I got this error and the replication has stopped. Pl= ease suggest about invalid resource manager ID.
 
Thanks,
Wasim


--
Muhammad Ikram

--=_d66191c9-4e20-4eec-80ab-e820421c9505--