Skip to content

Error Wal-fetch #426

Description

@rroux

Hello,
I'm currently testing a restore on one of the PostgreSQL dockers.
The backup works fine.
Restoring the full backup works, but not restoring the wal transaction files.
The restore works and after a few minutes, I have this type of error in the postgreSQL logs:

[2020-10-06 06:38:30 UTC] LOG: restored log file "00000001000009000000001B" from archive
[2020-10-06 06:38:30 UTC] LOG: server process (PID 733444) exited with exit code 2
[2020-10-06 06:38:30 UTC] LOG: terminating any other active server processes
[2020-10-06 06:38:30 UTC] FATAL: could not restore file "00000001000009000000001C" from archive: child process was terminated by signal 3: Quit
[2020-10-06 06:38:30 UTC] LOG: all server processes terminated; reinitializing
[2020-10-06 06:38:30 UTC] LOG: database system was interrupted while in recovery at log time 2020-09-21 01:21:10 UTC
[2020-10-06 06:38:30 UTC] HINT: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
[2020-10-06 06:38:30 UTC] LOG: starting point-in-time recovery to 2020-10-05 03:58:55+00 wal_e.operator.backup INFO MSG: promoted prefetched wal segment
`

Then, the restore loops over a few Wal files without stopping.

Here is my recovery.conf file:
restore_command = 'envdir /var/lib/postgresql/data/wal-e.d/env wal-e wal-fetch %f %p'
recovery_target_time = '2020-10-05 03:58:55'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions