Skip to content

ERROR: Thread [2]: WAL segment "..." is absent #435

Closed
@slothfk

Description

@slothfk

При выполеннии инкрементальной копии (PAGE) возникает ошибка из заголовка

ERROR: Thread [2]: WAL segment "/archive/postgresql/wal/servbd/000000010000119C000000FF" is absent
ERROR: Thread [1]: Interrupted during WAL reading

При этом "ошибочный" файл в каталоге журналов присутствует

$ sudo -u postgres find /archive/postgresql/wal/servbd/ -name '000000010000119C000000FF*'
/archive/postgresql/wal/servbd/000000010000119C000000FF.gz

А в журнале ПГ

INFO: pg_probackup archive-push WAL file: 000000010000119C000000FF, threads: 1/1, batch: 1/1, compression: zlib
INFO: pg_probackup archive-push completed successfully, pushed: 1, skipped: 0, time elapsed: 87ms

Вывод pg_probackup show

$ sudo -u postgres -i pg_probackup show --instance $(hostname -s) | head                                                    
==================================================================================================================================================
 Instance       Version  ID      Recovery Time           Mode  WAL Mode  TLI     Time    Data   WAL  Zratio  Start LSN      Stop LSN       Status 
==================================================================================================================================================
 servbd         11       R06POQ  ----                    PAGE  ARCHIVE   1/1   1m:19s       0     0    1.00  11A4/10482018  0/0            ERROR  
 servbd         11       R007G1  2021-09-25 22:57:08+03  FULL  ARCHIVE   1/0  57m:37s    74GB  80MB    1.83  119B/F000028   119B/148AAA10  OK     
 servbd         11       QZN8S1  2021-09-18 22:57:05+03  FULL  ARCHIVE   1/0  57m:37s    68GB  80MB    1.88  1184/32000028  1184/3765F7A8  OK     
 servbd         11       QZC4S1  2021-09-12 22:00:37+03  PAGE  ARCHIVE   1/1      38s    70MB  16MB    2.51  1177/2F000028  1177/300C0120  OK     
 servbd         11       QZAA41  2021-09-11 22:53:32+03  FULL  ARCHIVE   1/0   54m:3s    65GB  64MB    1.90  1176/B9000028  1176/BD75A4F8  OK     
 servbd         11       QZ8FG1  2021-09-10 22:01:39+03  PAGE  ARCHIVE   1/1   1m:41s   930MB  16MB    2.61  1176/9000028   1176/A1E1880   OK     
 servbd         11       QZ6KS1  2021-09-09 22:01:59+03  PAGE  ARCHIVE   1/1    2m:1s  1222MB  16MB    2.37  1173/D2000028  1173/D336A1B0  OK 

Вывод pg_probackup show --archive


ARCHIVE INSTANCE 'servbd'
=================================================================================================================================
 TLI  Parent TLI  Switchpoint  Min Segno                 Max Segno                 N segments  Size  Zratio  N backups  Status   
=================================================================================================================================
 1    0           0/0          000000010000113600000056  00000001000011A400000017  13040       82GB  2.48    26         DEGRADED 

Посмотрел по другим инстансам, по другим проектам, везде статус DEGRADED. Это нормально?

Вывод pg_probackup show-config

# Backup instance information
pgdata = /var/lib/pgpro/1c-11/data
system-identifier = 6926224934093253540
xlog-seg-size = 16777216
# Connection parameters
pgdatabase = backup
pghost = localhost
pguser = backup
# Replica parameters
replica-timeout = 5min
# Archive parameters
archive-timeout = 5min
# Logging parameters
log-level-console = INFO
log-level-file = OFF
log-filename = pg_probackup.log
log-rotation-size = 0TB
log-rotation-age = 0d
# Retention parameters
retention-redundancy = 2
retention-window = 30
wal-depth = 7
# Compression parameters
compress-algorithm = zlib
compress-level = 1
# Remote access parame

Пока собирал данные запустил создание копии с логами VERBOSE, и что странно, копия сделалась ...
Тут же запустил создание копии скриптом (который делает копии и по другим серверам - успешно), опять ошибка ...

Попробую выяснить в чем отличие, по результатам дополню информацией

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions