On Tue, Jan 16, 2024 at 3:53 PM Emanuel Calvo <3man...@gmail.com> wrote:
> > El mar, 16 ene 2024 a las 22:47, Brad White (<b55wh...@gmail.com>) > escribió: > >> Errors from the Primary server >> >> 2024-01-15 00:01:06.166 CST [1428] ERROR: requested WAL segment >> 0000000100000002000000A2 has already been removed >> 2024-01-15 00:01:06.166 CST [1428] STATEMENT: START_REPLICATION >> 2/A2000000 TIMELINE 1 >> 2024-01-15 00:01:11.158 CST [3472] ERROR: requested WAL segment >> 0000000100000002000000A2 has already been removed >> 2024-01-15 00:01:11.158 CST [3472] STATEMENT: START_REPLICATION >> 2/A2000000 TIMELINE 1 >> 2024-01-15 00:01:11.158 CST [3472] LOG: could not receive data from >> client: An existing connection was forcibly closed by the remote host. >> >> > These log entries mean that some node is requesting a WAL segment that was > already removed from > the server. > > 2024-01-15 01:14:02.884 CST [2552] LOG: started streaming WAL from >> primary at 2/A2000000 on timeline 1 >> 2024-01-15 01:14:02.884 CST [2552] FATAL: could not receive data from >> WAL stream: ERROR: requested WAL segment 0000000100000002000000A2 has >> already been removed >> 2024-01-15 01:14:02.884 CST [1792] LOG: waiting for WAL to become >> available at 2/A2002000 >> >> > > These are related to the backup not finding that segment, so it means > you'll need to resync > your backup stream. > You pointed me in the right direction. Turns out the files are still there, so it must be a permission issue. pgUser has full access to the files. Postgres is running as pgUser, except that wasn't true on the backup. Was running as 'Network Service'. Should be better now. Aaaand I'm wrong. Still getting the same errors on both servers.
