a year ago
No errors thrown.
Status says "Queued"
I've tried to redeploy after deployment staying stuck for hours.
Project id: 34191cb9-592a-499f-93d7-a85ef48feecb
Most recent entries in the Build Log
No files changed in this command, skipping snapshotting.
Pushed us-west1.registry.rlwy.net/ba55d932-09a5-4c74-8a89-91428311296c/cache@sha256:7c13c63c49a196816f9af1221f0054a912cd9cc3cd257c4b8a1225fdefc8c4f9
Pushed us-west1.registry.rlwy.net/ba55d932-09a5-4c74-8a89-91428311296c/cache@sha256:f8df7a97ed76c49153c6f254647f2ae0459cbeb5e79fa2bd6005e3b3ddbe5fa9
Pushing image to us-west1.registry.rlwy.net/ba55d932-09a5-4c74-8a89-91428311296c:a19a0c6d-634e-430d-b33d-6a6d544f46ca
Stopping Container
Pushed us-west1.registry.rlwy.net/ba55d932-09a5-4c74-8a89-91428311296c@sha256:91c3d97ce59e314fac170a324a9634f71ebfe4aa5ee9d02579f6a0007cfc4aa7
17 Replies
Note; a couple of months ago, deployment suddenly started failing in my project.
Brody fixed that particular issue back then, but I'm not sure if the issue I started facing yesterday has the same root cause:
Hello,
I've reverted the Nixpacks version for your service and your latest deployment has gone out successfully.
Best,
Brody
Most recent entries in Build Log as per Mar 9 8:44:56. It's been building for 38 minutes and still going.
Pushing [==================================================>] 733.5MB 60697b53c307
Pushing [==================================================>] 735.3MB 60697b53c307
Pushed 60697b53c307
c544f40b-547e-438c-b639-65116eb11ad8: digest: sha256:ff7127a022b50336e6c5acff5062d48a3af3534f8de8040189308cfce13e5ae9 size: 2422
Publish time: 34.80 seconds
a year ago
please do not tag the team, i am unfortunately not able to assist right now
Ok. Will stop tagging you. FYI: What I'm experiencing seems similar to this https://discord.com/channels/713503345364697088/1346585978231459891/1346585978231459891
a year ago
Your pre-deploy command failed, have you had time to look at the logs?
a year ago
something else to note -
you cannot run collectstatic (or anything that modifies the filesystem) in a pre-deploy command since the pre-deploy command is ran in a separate container from the runtime container, ive removed this for you.
you now have the pre-deploy command set to run a migration, but you also have your start command set to run a migration, you should remove the migration command from your start command
Thanks Brody. The Deploy Log didn't exist when I raised the issue. The build looked like it was in a "stuck" state - Build Logs was the only log available. Anyways, appreciate you taking the time to look into this. It's moving into Deploy now, and the deploy overall looks much better. Thanks.
I've updated my railway.json as per your feedback above:
{
"$schema": "https://railway.app/railway.schema.json",
"build": {
"builder": "NIXPACKS"
},
"deploy": {
"preDeployCommand": "python manage.py makemigrations && python manage.py migrate",
"startCommand": "python manage.py collectstatic --noinput && gunicorn sdeets.wsgi",
"restartPolicyType": "ON_FAILURE",
"restartPolicyMaxRetries": 10
}
}
a year ago
looks good to me, is it working?
a year ago
awsome, am i good to mark this as solved?
Yes, please tag it as solved.
Do you know what caused the deploy to get stuck? Is there anything else I can do on my end/code to prevent this from happening in the future?
a year ago
can you link to the specfic deployment that was stuck?
I attemted some few times, but I believe this is one example: f7c83018-dec6-45c2-a103-fcd4d6d8d37b
a year ago
no issues are standing out for me there