2nd PostgreSQL server in WAL shipping cluster fails to start

Dear all,

Some years ago I set up a two PostgreSQL 13 nodes cluster on Debian 11. This cluster uses the Write-Ahead Log Shipping method. I’ve just been told the second server (in standby mode) is down and refuses to start again with the following error message (roughly translated from French) :

2025-01-09 09:46:35.742 CET [3147382] FATAL:  could not receive data from WAL stream: ERROR:  segment requested from transaction journal, 000000010000000D000000D6, has already been removed

2025-01-09 09:46:40.745 CET [3147395] LOG:  journal flow started from primary at D/D6000000 on timeline 1

2025-01-09 09:46:40.745 CET [3147395] FATAL:  could not receive data from WAL stream : ERROR:  segment requested from transaction journal, 000000010000000D000000D6, has already been removed

2025-01-09 09:46:45.749 CET [3147397] LOG: journal flow started from primary at D/D6000000 on timeline 1

2025-01-09 09:46:45.749 CET [3147397] FATAL:  could not receive data from WAL stream : ERROR:  segment requested from transaction journal, 000000010000000D000000D6, has already been removed

2025-01-09 09:46:50.753 CET [3147424] LOG:  journal flow started from primary at D/D6000000 on timeline 1

2025-01-09 09:46:50.753 CET [3147424] FATAL:  could not receive data from WAL stream : ERROR:  segment requested from transaction journal, 000000010000000D000000D6, has already been removed

Would you have any idea how to fix this issue ?

Best regards,

Samuel