10 months ago
We are trying to use a backup for our data in postgres, but whenever it is mounted we see the error 2025-11-26 22:20:43.394 UTC [6] FATAL: bogus data in lock file "postmaster.pid": "�". But we can't access the volume to run rm /var/lib/postgresql/data/postmaster.pid. What can we do since all our data is on our backup.
2 Replies
10 months ago
The stale postmaster.pid file from the backup is blocking Postgres from starting. Since you can't shell into a crashed service, the easiest fix is to deploy a simple Alpine container, mount the same volume to it, run rm /var/lib/postgresql/data/postmaster.pid, then detach the volume and reattach it to your Postgres service. Alternatively, you could spin up a fresh Postgres instance and restore your backup there instead—that sidesteps the pid file issue entirely.
10 months ago
You still need to unmount the volume from the Postgres service and mount it to the Filebrowser template.
There's also no 'Volumes' tab in a service.
Please be careful with what you recommend to other users.
Status changed to Solved medim • 6 months ago