3 months ago
This service has been failing to deploy for 24 hours and I get no deploy logs from the startCommand - but I do from preDeployCommand.
I've tried rolling code back to the previous succesfully deployed git commit hash and it didn't work. I've tried deploying a simple "hello world" docker image and it didn't work. I've tried everything I can think of.
Help!
19 Replies
3 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
3 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
3 months ago
Identified a bug. Manually resolved for you. You should be good to redeploy!
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Thanks jake!
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Solved ironslob • 3 months ago
3 months ago
This is failing again in exactly the same way.
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Uhh. That's very odd. I've gone and reset that migration. Could you try again?
Status changed to Awaiting User Response Railway • 3 months ago
jake
Uhh. That's very odd. I've gone and reset that migration. Could you try again?
3 months ago
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Hmm looks like it was solved. But, I don't think we bubbled up an error
Was it an error with the predeploy command? That's what I'd assume
Status changed to Awaiting User Response Railway • 3 months ago
jake
Hmm looks like it was solved. But, I don't think we bubbled up an errorWas it an error with the predeploy command? That's what I'd assume
3 months ago
It started to work again, then it started to fail on the pre-deploy command ("alembic upgrade head"), and after resizing the volume it's now failing on ... something else?
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Hmm. I don't see any additional info that we have here. These are really weird errors you're running into. If you could potentially let us know what might be failing here, that would be huge
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Thanks Jake - it started again.
I simply hit redeploy and now it's working. Apologies, I assumed you had more context than I did.
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
(fixing double submit)
3 months ago
Looks like it's happening again - https://railway.com/project/40acf012-6fd7-4bf5-8cbc-ba051ed2327c/service/02d0adb3-40fa-473f-bb25-6322c1e45a2e?environmentId=015d922b-5dde-4503-ba29-30121cc3af25&id=586e0588-389e-4961-b3e6-f7852aa49737#deploy - am open to suggestions to fix this properly.
I am having to ssh into the container to run scripts - could it be one of them isn't cleaning up a filehandle, or something more exotic? Some context on the bug you mentioned might help me figure out if there's something my code is doing that's causing this.
3 months ago
Unfortunately, at this point, this flakeyness isn't observed under any other situations and thus has to be an application level issue
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
I'm not asking for any help with the application, as it works fine. The problem that I'm experiencing is obviously with your platform as you've mentioned a couple of times that the deployment was in a "buggy" state, or that you'd identified a bug with your software. What I'm saying is that if you can explain what's happening at your end to prevent my app from deploying (not running - deploying!) then perhaps there'll be something obvious at my end that might be triggering said bug, and then you can resolve your issue, and I can resolve mine.
Regardless, I'm still in a situation where I can't deploy my application intermittently, and right now it's out of service and it's becoming increasingly frustrating that I can't reliably deploy.
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
And now I just managed to re-deploy it again. Great, till it happens again...
3 months ago
Went and looked into it a bit more. I believe I might see an issue, however, we will need another sample of the last one to validate that this is indeed what's occuring
I'm very sorry that you've run into this a few times and that it's been frustrating
Status changed to Awaiting User Response Railway • 3 months ago
2 months 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 • 2 months ago
