Skip to content
Stuck after Build; Deploy not starting
a-lil-birb
OP

2 years ago

Project ID: 1b25cd0f-f9ea-4a0d-b9f9-77f61f9caea6

Build process is always done in 2 to 8 seconds, but Deploy never starts and it ends up failing (from time out?) after 5 minutes or so.

Build log is complete with Publish time: x.xx seconds at the end. Deploy logs empty as expected since it claims to have not started.

Project was initially deployed successfully earlier today before env variables were added.

Closed

35 Replies

2 years ago

The affected project uses Node.js and does not have the new build system beta enabled, in case that is relevant.


2 years ago

is there is some limit on the size of environment variables? Some of the ones that were set before the issue occurred are quite long


2 years ago

there's been ongoing issues despite no current open incidents, you can usually get it to go through by canceling that deployment and pushing another deployment


2 years ago

since this issue started it has consistently done this, but I will try to redeploy


2 years ago

ctrl / cmd + k -> deploy latest commit


2 years ago

on a phone atm


2 years ago

i found the option in the menu, but it doesn’t seem to have changed anything, still stuck deploying with no deploy logs.


2 years ago

have you canceled the current deploy?


2 years ago

all deploys are Removed currently


2 years ago

try to deploy the latest commit again?


2 years ago

issue persists, it has been stuck deploying with no logs for a minute now


2 years ago

how long does the build itself take?


2 years ago

seconds


2 years ago

would you happen to know the size of the image?


2 years ago

how would I find that


2 years ago

in the build logs


2 years ago

the size it shows in the last pushing log (17.35mb) or the size: without a unit (2417)?


2 years ago

are you and the OP of this thread on the same team?


2 years ago

it is the same project, id 1b25cd0f-f9ea-4a0d-b9f9-77f61f9caea6


2 years ago

gotcha


2 years ago

!t


2 years ago

This thread has been escalated to the Railway team.

Status changed to Awaiting Railway Response brody • over 2 years ago


2 years ago

A lot of my deployments now also are getting stuck on creating container with no logs.


2 years ago

Looks like redeploying the "stuck" deploy and then aboring the "stuck" deploy resolves my issue.


alvarin

2 years ago

Same problem for some of our deployments.

Some deployment ids:

1. 4b1673ff-a95b-4b39-86ab-02a0bab14a8f

2. 8e489dcd-9f62-4d04-9c94-b24410258bf9

Redeploying or restarting is not solving the problem.


2 years ago

Also still "taking snapshot of code" for multiple services.

1263816045827985470


alvarin

2 years ago

https://station-media-server.railway.app/attachments/f5f64b4bfad94b93b0201585d2680c99-image.pngThe error persists.

(snapshot from deployment e7cb215b-de6c-4f0c-963b-0d5265aca42e)


We've investigated, and this is the cause for the issue you're seeing here


We're looking at addressing this in the future, but the short term move to unblock you here will be to reduce the length of the variables


2 years ago

oh! I’ll have to move them elsewhere. I was using them to quickly replace some git ignored json files (probably bad practice but I had to quickly do it lol)


Great! Please confirm that moving those variables elsewhere unblocks you


2 years ago

just curious, how long byte wise are these variables?


2 years ago

one was like 50kb (it was a super hacky workaround to “i can’t put my secrets.json in easily and my laptop broke and editing the code significantly on a phone is a bad idea”)


2 years ago

could you transition to loading your secrets as regular environment variables?


2 years ago

I will look into that


2 years ago

ok the project does deploy but it crashes because I did not make some necessary code changes yet


Welcome!

Sign in to your Railway account to join the conversation.

Loading...