2 months ago
Container builds, but fails to start. Attempting previous known working builds fails with the same error. Disabling Metal yields same result.
4 Replies
2 months ago
!t
2 months ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response uxuz • 2 months ago
2 months ago
Hi there,
Could you please indicate which service specifically in the project you're referring to - is it your backend service?
Additionally, what happens if you restart the deployment?
Lastly, could you please share any deploy logs you see? I just see "starting container", but wondering if you have any other app-specific logs on your end.
Best,
The Railway Team
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Apologies for the delayed response. It was the backend service. No logs visible, restarting deployment of the service using previous commit and latest commit resulted in the same error. I ended up duplicated the service, it successfully built and started. I then replaced the the failing one.
Not sure, but I think we were caught by the Metal migration and something happened.
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Hi there,
Glad to hear you've got it sorted and apologies for the inconvenience!
Best,
The Railway Team
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Solved sarahkb125 • 2 months ago