agora inbox for pgsql-admin@postgresql.org
help / color / mirror / Atom feedWAL file corruption on standby PostgreSQL
6+ messages / 6 participants
[nested] [flat]
* WAL file corruption on standby PostgreSQL
@ 2024-07-22 18:26 Wasim Devale <wasimd60@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Wasim Devale @ 2024-07-22 18:26 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>; pgsql-admin
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: WAL file corruption on standby PostgreSQL
@ 2024-07-22 18:42 Muhammad Ikram <mmikram@gmail.com>
parent: Wasim Devale <wasimd60@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Muhammad Ikram @ 2024-07-22 18:42 UTC (permalink / raw)
To: Wasim Devale <wasimd60@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>; pgsql-admin
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: WAL file corruption on standby PostgreSQL
@ 2024-07-22 19:24 vrms <vrms@netcologne.de>
parent: Muhammad Ikram <mmikram@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: vrms @ 2024-07-22 19:24 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
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
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: WAL file corruption on standby PostgreSQL
@ 2024-07-22 22:20 Jean-Paul POZZI <jp.pozzi@izzop.net>
parent: vrms <vrms@netcologne.de>
0 siblings, 1 reply; 6+ messages in thread
From: Jean-Paul POZZI @ 2024-07-22 22:20 UTC (permalink / raw)
To: vrms <vrms@netcologne.de>; +Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: WAL file corruption on standby PostgreSQL
@ 2024-07-23 06:52 Mahendra Singh <msmahendrasingh18@gmail.com>
parent: Jean-Paul POZZI <jp.pozzi@izzop.net>
0 siblings, 1 reply; 6+ messages in thread
From: Mahendra Singh @ 2024-07-23 06:52 UTC (permalink / raw)
To: Jean-Paul POZZI <jp.pozzi@izzop.net>; +Cc: vrms <vrms@netcologne.de>; pgsql-admin <pgsql-admin@lists.postgresql.org>
Try to reset the wal using '*pg_resetwal*'.
https://www.postgresql.org/docs/current/app-pgresetwal.html
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
>
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: WAL file corruption on standby PostgreSQL
@ 2024-07-23 11:29 Muhammad Imtiaz <imtiazpg712@gmail.com>
parent: Mahendra Singh <msmahendrasingh18@gmail.com>
0 siblings, 0 replies; 6+ messages in thread
From: Muhammad Imtiaz @ 2024-07-23 11:29 UTC (permalink / raw)
To: Mahendra Singh <msmahendrasingh18@gmail.com>; +Cc: Jean-Paul POZZI <jp.pozzi@izzop.net>; vrms <vrms@netcologne.de>; pgsql-admin <pgsql-admin@lists.postgresql.org>
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*
*Email: imtiaz.m@bitnine.net <imtiaz.m@bitnine.net>*
On Tue, Jul 23, 2024 at 11:50 AM Mahendra Singh <msmahendrasingh18@gmail.com>
wrote:
> Try to reset the wal using '*pg_resetwal*'.
>
> https://www.postgresql.org/docs/current/app-pgresetwal.html
>
>
> 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
>>
>>
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2024-07-23 11:29 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-07-22 18:26 WAL file corruption on standby PostgreSQL Wasim Devale <wasimd60@gmail.com>
2024-07-22 18:42 ` Muhammad Ikram <mmikram@gmail.com>
2024-07-22 19:24 ` vrms <vrms@netcologne.de>
2024-07-22 22:20 ` Jean-Paul POZZI <jp.pozzi@izzop.net>
2024-07-23 06:52 ` Mahendra Singh <msmahendrasingh18@gmail.com>
2024-07-23 11:29 ` Muhammad Imtiaz <imtiazpg712@gmail.com>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox