20 days ago
Hello Railway Support,
My production service, ChessReview.online, is repeatedly failing to build with this error:
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" >
I have retried deployment, but the same infrastructure error persists. The failure occurs during image building, before the application build can complete.
Service: Chess-Game-Reviewer
Region: US West (California)
Latest failed deployment: https://railway.com/project/bde918cb-4c24-4dfe-aa08-17efb729fd27/service/2cb732c8-bfca-4ecf-8192-6ead050fa7d4?environmentId=22e4880a-9e86-453d-9fad-05580a93aa19&id=ef875814-95f4-4237-bf25-b0562bd48207#build
This is blocking a production homepage fix that has already been committed to the main branch. Please investigate the BuildKit worker/daemon failure and advise how to get this service building and deploying successfully.
Thank you.
3 Replies
Status changed to Awaiting Railway Response Railway • 20 days ago
20 days ago
This is on our side. There is an active incident on our build infrastructure (https://status.railway.com/incident/ILLVW9WG, "Builds failing in US West"): builds are failing before any of your build steps run, with the build daemon connection dropping or the build machine never coming up, which is exactly what your deployments show. Your source, build configuration and dependencies are not at fault, and nothing needs to change on your end.
Running services are not affected. A fresh deployment of the same commit may get through in the meantime; otherwise please follow the status page for the all-clear, and redeploy once it is posted.
Status changed to Awaiting User Response Railway • 20 days ago
20 days ago
Sorry for the trouble. The build failures you're seeing ("build daemon returned an error" before any build step runs) are caused by an issue with our build infrastructure in US West, not by anything in your project or code. You don't need to change anything on your side.
We're working on a fix and tracking it here: https://status.railway.com/incident/ILLVW9WG
Your running services aren't affected. Redeploying may work in the meantime, but it can fail again until the fix is in. Once the incident is resolved, redeploying the same commit should build normally.
20 days ago
The issue causing builds to fail in US West has been resolved. Builds are now completing normally. If a build failed during this incident, redeploying it should now succeed.
13 hours 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 • about 13 hours ago