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 1sVycV-00Cbyo-L1 for pgsql-admin@arkaria.postgresql.org; Mon, 22 Jul 2024 19:22:51 +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 1sVycT-00665H-BX for pgsql-admin@arkaria.postgresql.org; Mon, 22 Jul 2024 19:22:49 +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 1sVycS-006659-U0 for pgsql-admin@lists.postgresql.org; Mon, 22 Jul 2024 19:22:49 +0000 Received: from cc-smtpout1.netcologne.de ([89.1.8.211]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sVycP-000ugY-Rs for pgsql-admin@lists.postgresql.org; Mon, 22 Jul 2024 19:22:48 +0000 Received: from cc-smtpin1.netcologne.de (cc-smtpin1.netcologne.de [89.1.8.201]) by cc-smtpout1.netcologne.de (Postfix) with ESMTP id F30E912ABF for ; Mon, 22 Jul 2024 21:22:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1721676162; bh=rUD7UEzI5Lw/mS+eYoPlf6YC5Ue6HHli80Vrv7gvr/Y=; h=Message-ID:Date:Subject:To:References:From:In-Reply-To:From; b=GjPGB3rtJtIb911ATeI5cT5VtoRo+Jk2gi0n1zlD92WYq8yCahzMIlKntISEqe9Ou pTTmODpOrKm9CSQvK9/lo0DiqfD+SygZZ399jfmfG2Ee6L8+NbBhvNlWdMBS34UenI k4PRiyRs37Sp1VH78HYLCEhtux+JpkgS5WFbUJttsH3r2rZq5w2btCKy/7WbwhteQA +PKOcZPE0O+xZQI6952SN1JD5zMpYu8l0HIaA/JlM0acjauYlPmT5D9d9hoBRK/irn jDlqyzRLj05Z8eCxEeqIW5GGLTtO5ePSBeUgyjeYpZMGs+LgAx0MwhFu6NXfgM4/Fk 40cPPsjTEXidg== Received: from [IPV6:2a03:b580:af0d:f901:cece:ad36:6ea3:f071] (unknown [IPv6:2a03:b580:af0d:f901:cece:ad36:6ea3:f071]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by cc-smtpin1.netcologne.de (Postfix) with ESMTPSA id C398511D87 for ; Mon, 22 Jul 2024 21:22:41 +0200 (CEST) Content-Type: multipart/alternative; boundary="------------try2USNI76nshrR1fGrKFj1O" Message-ID: <0322e728-fe36-45a4-9667-299246028db8@netcologne.de> Date: Mon, 22 Jul 2024 21:24:50 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: WAL file corruption on standby PostgreSQL To: pgsql-admin@lists.postgresql.org References: Content-Language: en-US From: vrms In-Reply-To: X-NetCologne-Spam: L X-Spamd-Bar: - X-Rspamd-Action: no action X-Rspamd-Queue-Id: C398511D87 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------try2USNI76nshrR1fGrKFj1O Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 caused corruption of WAL archives. > > Regards > Muhammad Ikram > > > > On Mon, Jul 22, 2024 at 11:26 PM Wasim Devale wrote: > > Hi All > > 2024-07-22 11:15:10 PDT [1723]: [7028-1] user=,db=,app=,client= > LOG:  restored log file "000000010000170900000081" from archive > 2024-07-22 11:15:10 PDT [1723]: [7029-1] user=,db=,app=,client= > LOG:  invalid resource manager ID 128 at 1709/8183BFA8 > 2024-07-22 11:15:10 PDT [1723]: [7030-1] user=,db=,app=,client= > LOG:  invalid resource manager ID 128 at 1709/8183BFA8 > > > I got this error and the replication has stopped. Please suggest > about invalid resource manager ID. > > Thanks, > Wasim > > > > -- > Muhammad Ikram > --------------try2USNI76nshrR1fGrKFj1O Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 caused corruption of WAL archives.

Regards
Muhammad Ikram



On Mon, Jul 22, 2024 at 11:26 PM Wasim Devale <wasimd60@gmail.com> wrote:
Hi All

2024-07-22 11:15:10 PDT [1723]: [7028-1] user=,db=,app=,client= LOG:  restored log file "000000010000170900000081" from archive
2024-07-22 11:15:10 PDT [1723]: [7029-1] user=,db=,app=,client= LOG:  invalid resource manager ID 128 at 1709/8183BFA8
2024-07-22 11:15:10 PDT [1723]: [7030-1] user=,db=,app=,client= LOG:  invalid resource manager ID 128 at 1709/8183BFA8


I got this error and the replication has stopped. Please suggest about invalid resource manager ID.

Thanks,
Wasim


--
Muhammad Ikram

--------------try2USNI76nshrR1fGrKFj1O--