31.01.2026 19:08, Álvaro Herrera пишет:
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
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?
May be this is the reason for the first message and this is not a bug. This can be with NFS.
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
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.
The bug is here.
basic_archive lost the value and was empty. But show all; show that the value is.
