My database keeps crashing
pegasusmkd
HOBBYOP

a month ago

I have not committed any changes or deployments recently, especially not the database.

I am using the standard database image provided by Railway.

It apparently first crashed 18 hours ago, but, it is still crashing.

I just tried to re-deploy it, but it crashes with the same issue.

The logs are


Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d6950f1f-8ed9-4dce-bc11-a7367ad06ffd/vol_91q739s16khekxz2

ERROR (catatonit:2): failed to exec pid1: No such file or directory
Awaiting Railway Response

2 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


sam-a
EMPLOYEE

a month ago

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.

It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.

You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY

If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c

Feel free to respond if your question has not been addressed.


Status changed to Awaiting User Response Railway about 1 month ago


dispencer
PRO

a month ago

Absolutely ridiculous. Im leaving this service.


Status changed to Awaiting Railway Response Railway about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...