Deployments are stuck at the initialization phase
chrislbrown84
PROOP

4 months ago

Hello,

I am trying to deploy three services, and they are both stuck at the Initialization phase. Specifically, the deployment status is:

"Deployment in progress: Taking a snapshot of the code..."

I believe it could be related to this incident: https://railway.instatus.com/clygezlse309640h2ohwh52a1fq

I have tried re-firing the deployments several times without success.

Thanks!

Solved

9 Replies

sam-a
EMPLOYEE

4 months ago

Hey! We had a Metal builder experiencing issues earlier today that was causing builds to get stuck in the queue. Your build was waiting to be picked up but the builder wasn't processing it.

This has since resolved and your latest deployments went through successfully. If you run into this again, cancelling and redeploying will usually route your build to a different builder.

Apologies for the disruption!


Status changed to Awaiting User Response Railway 4 months ago


chrislbrown84
PROOP

3 months ago

same issue again today it seems. have tried restarts 5+ times, no luck.


Status changed to Awaiting Railway Response Railway 3 months ago


chrislbrown84
PROOP

3 months ago

just to expand the feedback (not because i'm mad, just to help you with awareness) - i did try many multiple restarts and whatever i did it didnt seem to pick up a different build server. Possibly 10 restarts and it just wouldnt go through. I went outside and enjoyed some fresh air and 4 hours later i think you fixed the build server as it ran fine. Today i've had the same issue.

thanks


sam-a
EMPLOYEE

3 months ago

Thanks for the info. Can you provide links to the affected service(s)?


Status changed to Awaiting User Response Railway 3 months ago


chrislbrown84
PROOP

3 months ago

deploymentid e5ee10d2-d301-48b6-92b6-9910d021eb33


Status changed to Awaiting Railway Response Railway 3 months ago


chrislbrown84
PROOP

3 months ago

same issue again today - 233e35c0-f3b3-4548-aa26-92daccc3f342


chrislbrown84

same issue again today - 233e35c0-f3b3-4548-aa26-92daccc3f342

3 months ago

Your toml file config is invalid:

Failed to parse TOML file railway.toml:\n(1, 1): parsing error: keys cannot contain \u0000 character

So the deployment never made it to the build stage.


Status changed to Awaiting User Response Railway 3 months ago


ray-chen

Your toml file config is invalid: ``` Failed to parse TOML file railway.toml:\n(1, 1): parsing error: keys cannot contain \u0000 character ``` So the deployment never made it to the build stage.

chrislbrown84
PROOP

3 months ago

my bad. many thanks for the support.


Status changed to Awaiting Railway Response Railway 3 months ago


3 months ago

No worries! We should be surfacing that error up.


Status changed to Awaiting User Response Railway 3 months ago


Status changed to Solved ray-chen 3 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...