BUG #16830: Start of standby server never happens

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: oleg(dot)kiriyenko(at)gmail(dot)com
Subject: BUG #16830: Start of standby server never happens
Date: 2021-01-19 15:08:15
Message-ID: 16830-1603b03b6109f24d@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16830
Logged by: Олег Кириенко
Email address: oleg(dot)kiriyenko(at)gmail(dot)com
PostgreSQL version: 11.10
Operating system: Windows 2012 R2
Description:

When starting standby server it tries to read WAL from primary server but
freezes on the same record.
Logs below are in russian so i'll translate.

invalid record length at 42/99074DF0: wanted 24, got 0 ...

The problem is that standby never starts. It will repeat this message every
"wal_retrieve_retry_interval" (10 seconds here) with no progress. After
enabling debug logs I got warning "mapped win32 error code 2 to 2". Which is
not informative how to fix the error.

2021-01-19 16:16:27.929 MSK [4656] СООБЩЕНИЕ: неверная длина записи по
смещению 42/99074DF0: ожидалось 24, получено 0
2021-01-19 16:16:27.929 MSK [4656] ОТЛАДКА: mapped win32 error code 2 to
2
2021-01-19 16:16:27.948 MSK [2180] ОТЛАДКА: shmem_exit(1): 1
before_shmem_exit callbacks to make
2021-01-19 16:16:27.949 MSK [2180] ОТЛАДКА: shmem_exit(1): 4 on_shmem_exit
callbacks to make
2021-01-19 16:16:27.949 MSK [2180] ОТЛАДКА: proc_exit(1): 2 callbacks to
make
2021-01-19 16:16:27.949 MSK [2180] ОТЛАДКА: exit(1)
2021-01-19 16:16:27.949 MSK [2180] ОТЛАДКА: shmem_exit(-1): 0
before_shmem_exit callbacks to make
2021-01-19 16:16:27.949 MSK [2180] ОТЛАДКА: shmem_exit(-1): 0 on_shmem_exit
callbacks to make
2021-01-19 16:16:27.949 MSK [2180] ОТЛАДКА: proc_exit(-1): 0 callbacks to
make
2021-01-19 16:16:27.950 MSK [2804] ОТЛАДКА: reaping dead processes
2021-01-19 16:16:37.929 MSK [4656] ОТЛАДКА: switched WAL source from stream
to archive after failure
2021-01-19 16:16:37.929 MSK [4656] ОТЛАДКА: неверная длина записи по
смещению 42/99074DF0: ожидалось 24, получено 0
2021-01-19 16:16:37.929 MSK [4656] ОТЛАДКА: switched WAL source from
archive to stream after failure
2021-01-19 16:16:37.929 MSK [4656] СООБЩЕНИЕ: неверная длина записи по
смещению 42/99074DF0: ожидалось 24, получено 0
2021-01-19 16:16:37.929 MSK [4656] ОТЛАДКА: mapped win32 error code 2 to
2
2021-01-19 16:16:37.948 MSK [3984] ОТЛАДКА: shmem_exit(1): 1
before_shmem_exit callbacks to make
2021-01-19 16:16:37.949 MSK [3984] ОТЛАДКА: shmem_exit(1): 4 on_shmem_exit
callbacks to make
2021-01-19 16:16:37.949 MSK [3984] ОТЛАДКА: proc_exit(1): 2 callbacks to
make
2021-01-19 16:16:37.949 MSK [3984] ОТЛАДКА: exit(1)
2021-01-19 16:16:37.949 MSK [3984] ОТЛАДКА: shmem_exit(-1): 0
before_shmem_exit callbacks to make
2021-01-19 16:16:37.949 MSK [3984] ОТЛАДКА: shmem_exit(-1): 0 on_shmem_exit
callbacks to make
2021-01-19 16:16:37.949 MSK [3984] ОТЛАДКА: proc_exit(-1): 0 callbacks to
make
2021-01-19 16:16:37.951 MSK [2804] ОТЛАДКА: reaping dead processes

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Borodin 2021-01-19 17:12:39 Re: Reproducible GIST index corruption under concurrent updates
Previous Message Duncan Sands 2021-01-19 11:15:57 Reproducible GIST index corruption under concurrent updates