Re: basic_archive lost archive_directory
Álvaro Herrera <alvherre@kurilemu.de>
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Олег Самойлов <splarv@ya.ru>
Cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2026-01-31T16:08:10Z
Lists: pgsql-bugs
On 2026-Jan-29, Олег Самойлов wrote: > 2026-01-23 18:46:49.970 MSK,,,12085,,697397e9.2f35,1,,2026-01-23 18:46:49 > MSK,,0,WARNING,22023,"invalid value for parameter > ""basic_archive.archive_directory"": ""/mnt/ocean/postgres/stars/ > WAL""","Specified archive directory does not exist.",,,,,,,,"","archiver",,0 > 2026-01-23 18:57:23.589 MSK,,,12085,,697397e9.2f35,2,,2026-01-23 18:46:49 > MSK,,0,WARNING,01000,"""archive_mode"" enabled, yet archiving is not > configured","basic_archive.archive_directory is not > set.",,,,,,,,"","archiver",,0 Most likely, the NFS mount was lost for some reason. Did you check the kernel logs? Did you ask your colleagues if they unmounted the filesystem for laughs? Did you search for any funny logs on the NFS server side? > And directory existed and it has old WAL files (before error raised). > The basic_archive is unstable, but I don't know how to repeat this. It's difficult to believe that it was basic_archive's fault; it's just giving you whatever the kernel reported to a stat() call for the directory. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "¿Qué importan los años? Lo que realmente importa es comprobar que a fin de cuentas la mejor edad de la vida es estar vivo" (Mafalda)
Commits
-
basic_archive: Allow archive directory to be missing at startup.
- f510577de4f5 17.10 landed
- cc774c543b23 19 (unreleased) landed
- bde9ad31515a 18.4 landed
- 8fc45ac5d91a 15.18 landed
- 28c2b789652a 16.14 landed