I followed your workaround but the restored database still won't start. The logs show:
olgend
PROOP

2 months ago

FATAL: bogus data in lock file "postmaster.pid"

This is a stale lock file from the crash. Can you either:

  1. Delete the postmaster.pid file from the volume

  2. Or provide a direct download link for my backup so I can restore it locally

$10 Bounty

2 Replies

Railway
BOT

2 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

brody
EMPLOYEE

2 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody • 2 months ago

thaumanovic
PRO

2 months ago

If this container keeps crashing, you'll need to stop it, detach the volume, and then attach it to another container that will run stable. Then, using the Railway CLI, you can SSH into this container and delete the file yourself.

Alternatively, you could temporarily change the start command of this service to run rm and remove it that way.

Loading...