Skip to content
Deployments are really slow this morning
nicolasmi214
OP

25 days ago

Hi,

This morning deployments are super slow and even get stuck. The agent confirmed it's not on my side. Someone else has issues ? Is there a platform problem ongoing ?

Regards.

Solved

14 Replies

Railway
BOT

25 days ago

Two of your current deployments built and ran their pre-deploy steps in under a minute, then stalled while starting the container. One has been stuck at that step for about 15 minutes and the other for about 9 minutes, and your application code has not started in either one yet.

At that point in the deploy, your code, variables and settings have no effect, so changing them will not help. Cancelling a stuck deployment frees its slot, and a fresh deploy will retry starting the container.


Status changed to Awaiting User Response Railway • 25 days ago


nicolasmi214
OP

25 days ago

Sorry I didn't understand what you meant... what is the exact cause of the slowliness ? It's on my side ?


Status changed to Awaiting Railway Response Railway • 25 days ago


Railway
BOT

25 days ago

No, nothing we can see points to your side. Your newest deployment, on apex_v2, built normally and then stopped at the step where we start the container. That happens before your application runs at all, so your code, variables and settings can't cause it, and changing them won't help.

We haven't found what is holding up the container start, and we can't name the exact cause yet. Cancelling the stuck deployment frees its slot, and a fresh deploy will try starting the container again.


Status changed to Awaiting User Response Railway • 25 days ago


Railway

No, nothing we can see points to your side. Your newest deployment, on apex_v2, built normally and then stopped at the step where we start the container. That happens before your application runs at all, so your code, variables and settings can't cause it, and changing them won't help. We haven't found what is holding up the container start, and we can't name the exact cause yet. Cancelling the stuck deployment frees its slot, and a fresh deploy will try starting the container again.

roryfmc

25 days ago

So are deployments currently degraded?


Status changed to Awaiting Railway Response Railway • 25 days ago


Status changed to Awaiting User Response Railway • 25 days ago


djf1982

25 days ago

I'm seeing the same issues too


Status changed to Awaiting Railway Response Railway • 25 days ago


Status changed to Awaiting User Response Railway • 25 days ago


jjcsummerdown

25 days ago

Me too. Two deployments have taken 6+ minutes for some small tweaks


Status changed to Awaiting Railway Response Railway • 25 days ago


Status changed to Awaiting User Response Railway • 25 days ago


himanshuinnostax

25 days ago

we saw, builds are failing Build Failed: build daemon returned an error < listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: raw-read unix @->/run/buildkit/buildkitd.sock: use of closed network connection" >


Status changed to Awaiting Railway Response Railway • 25 days ago


Status changed to Awaiting User Response Railway • 25 days ago


nicolasmi214
OP

25 days ago

It's very random, 20 minutes ago 2 deployments was ok in a reasonable timing and now it's stuck again.


Status changed to Awaiting Railway Response Railway • 25 days ago


Railway
BOT

25 days ago

We're sorry for the trouble. We're currently investigating Slow build snapshot uploads in EU West (Amsterdam), which affects builds in that region, the region your service deploys to, so builds there can take longer than usual to start and timings can vary a lot from one deploy to the next.

Separately, your newest deployment on apex_v2 built and has now been waiting at the container start step for about 12 minutes, which, as before, happens before your application runs, so it is not caused by your code or settings.


Status changed to Awaiting User Response Railway • 25 days ago


scottie-capturra

25 days ago

My builds are not just slow they are failing with the same error: < listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: raw-read unix @->/run/buildkit/buildkitd.sock: use of closed network connection" >


Status changed to Awaiting Railway Response Railway • 25 days ago


Status changed to Awaiting User Response Railway • 25 days ago


scottie-capturra

25 days ago

Deployments now also failing with this error: The image "production-dpams.railway-registry.com/xxxx-…-4da1" could not be pulled from the registry. If the image is private, check that the registry credentials saved for this service are still valid.


Status changed to Awaiting Railway Response Railway • 25 days ago


Status changed to Awaiting User Response Railway • 25 days ago


scottie-capturra

Deployments now also failing with this error: The image "production-dpams.railway-registry.com/xxxx-…-4da1" could not be pulled from the registry. If the image is private, check that the registry credentials saved for this service are still valid.

badrlaajali

25 days ago

Same problem


Status changed to Awaiting Railway Response Railway • 25 days ago


Status changed to Awaiting User Response Railway • 25 days ago


victoria-essien

25 days ago

Mine are failing too. We'd be lucky if this doesn't take another 24 hours to fix


Status changed to Awaiting Railway Response Railway • 25 days ago


Status changed to Awaiting User Response Railway • 25 days ago


scottie-capturra

25 days ago

Mine are failing at all different points now without an error message even


Status changed to Awaiting Railway Response Railway • 25 days ago


Status changed to Awaiting User Response Railway • 25 days ago


Railway
BOT

18 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 18 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...