Skip to content
Can't deploy the service, no logs
viloder
OP

21 days ago

Hi, I can't deploy the service (bot) and there are no logs either in deployment, or building. It failed right away after I pushed deployment button.

The bot has been successfully running for several months, and deployment was working well. Nothing has been changed in the bot through this time.

What is the problem?

Other services are deployed successfully, no problem at all.

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 21 days ago


dizzydes90
EMPLOYEE

21 days ago

Hi,

We've looked at the five attempts from this afternoon (13:47 to 14:14 UTC). Each one is a redeploy of the same commit (537992e), passes the code snapshot step, and then fails two to four seconds into the build step with a generic failure before a builder is ever assigned, which is why both the build and deploy logs are empty. Nothing in your bot's code or configuration is being executed at that point, so it isn't something the bot is doing wrong, and your other services deploying fine fits that. For context, the deployment that had been running since April was removed at 05:58 UTC this morning, which is presumably what prompted the redeploys; if you didn't stop it yourself, tell us and we'll look at that as well.

One thing to try that separates the two likely causes: instead of the Redeploy button, trigger a fresh deployment from the source, either by pushing a new commit (an empty commit is enough) or by using Deploy Latest Commit on the service. A fresh deployment takes a new snapshot of the code rather than reusing the stored one. If that goes through, the stored snapshot the redeploys were reusing is the problem and we'll take that up on our side; if it fails the same way, reply here and we'll trace the failing step with the new deployment id.


Status changed to Awaiting User Response Railway • 21 days ago


viloder
OP

21 days ago

Yes, the empty commit helped! Thank you!

Yeah, I didn't stop service by myself, so it stopped most probably due to credit card issue (the payment did't pass). And during this stop maybe smth went wrong.

Anyway, now it's working, thank you for helping!


Status changed to Awaiting Railway Response Railway • 21 days ago


Status changed to Solved viloder • 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...