Postgres Pro
Downloads
Home   >   mailing lists

Thread: WAL file corruption on standby PostgreSQL

WAL file corruption on standby PostgreSQL

From
Wasim Devale
Date:
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

Re: WAL file corruption on standby PostgreSQL

From
Muhammad Ikram
Date:
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

Re: WAL file corruption on standby PostgreSQL

From
vrms
Date:
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

RE: WAL file corruption on standby PostgreSQL

From
Jean-Paul POZZI
Date:

Hello,

 

Some traces in Postgres or system logs ?

 



De: "vrms" <vrms@netcologne.de>
À: "undefined" <pgsql-admin@lists.postgresql.org>
Envoyé: 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 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

Re: WAL file corruption on standby PostgreSQL

From
Mahendra Singh
Date:
Try to reset the wal using 'pg_resetwal'. 



On Tue, Jul 23, 2024 at 2:20 AM Jean-Paul POZZI <jp.pozzi@izzop.net> wrote:

Hello,

 

Some traces in Postgres or system logs ?

 



De: "vrms" <vrms@netcologne.de>
À: "undefined" <pgsql-admin@lists.postgresql.org>
Envoyé: 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 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

Re: WAL file corruption on standby PostgreSQL

From
Muhammad Imtiaz
Date:
Hi,

 Consider the  pg_rewind utility to synchronize the standby with the primary node, ensuring the primary node is in a consistent state.  


Muhammad Imtiaz

PostgreSQL Technical Support Lead / Pakistan R&D

Mobile: +923345072521

On Tue, Jul 23, 2024 at 11:50 AM Mahendra Singh <msmahendrasingh18@gmail.com> wrote:
Try to reset the wal using 'pg_resetwal'. 



On Tue, Jul 23, 2024 at 2:20 AM Jean-Paul POZZI <jp.pozzi@izzop.net> wrote:

Hello,

 

Some traces in Postgres or system logs ?

 



De: "vrms" <vrms@netcologne.de>
À: "undefined" <pgsql-admin@lists.postgresql.org>
Envoyé: 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 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