Hanging Requests
Hi, my API requests are suddenly hanging (i.e. not resolving at all), is anyone else experiencing this? Server is EU-West.
Project ID:
c61c1785-a8d8-43d0-9d8b-6bd1f69aa3bSolution:Jump to solution
yep perfect.
looks like you got caught on a box that was having maintenance done on it.
it also looks like every deploy since has not failed, so if you see this again please bring it back up!...
25 Replies
Project ID:
c61c1785-a8d8-43d0-9d8b-6bd1f69aa3bfc61c1785-a8d8-43d0-9d8b-6bd1f69aa3bfNew reply sent from Help Station thread:
Similar issue, but only occassionallyYou're seeing this because this thread has been automatically linked to the Help Station thread. New reply sent from Help Station thread:
Seems to have resolved itself now, service was down ~15 minsYou're seeing this because this thread has been automatically linked to the Help Station thread.
I'm still periodically experiencing these errors and I think they're causing new builds to fail because it can't ping the healthcheck API and just times out. Is there any way for the railway team to look into this because it's becoming a bit of a deal-breaker?
Hey, we would need a minimal reproducible example to be able to look into it
So my current project just won't build at all (it says Successfully Built in the logs but the UI is showing the Build Error Icon) and I haven't changed any config settings (I've even tried removing the healthcheck to see if that would help but hasn't), in addition to that my previous build is not accepting any API calls.
I really don't know how to resolve this as the previous build (~4 hours ago) was working fine and it's just suddenly out of the blue stopped building/accepting API requests with no indication as to why. I can share build logs if that would help?
please share the build logs
yes, I will take a look when I'm back at my computer
Appreciate it!
without looking at it, my initial thoughts because there only been 2 people reporting it, is that it's an issue with the application itself
So after just rebooting the container almost a dozen times it's now seemed to build fine, I agree if it's just 2 users there's likely something we're doing that's wrong but the frustrating thing is there's no error logs indicating any issues and this would just hang the API requests indicating it can't resolve the host (else it would return at least some kind of response). I've recently moved over to EU West if that helps (maybe the other user has done something similar)?
railway wouldnt have any more visibility into what your code is or is not doing then you would, aka if you want that observability you would need to be logging that information
this didnt show me anything that was failing? can you provide a deep link to the build logs for a deployment that failed?
That's the deployment that failed, this is where I'm getting confused where the build logs say "Success" but the UI is showing "Failed" (see screenshot) and the service suddenly isn't accessible
can you provide a deep link to those build logs
Railway
Railway
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
im sorry but that doesnt bring me to anything that shows any errors
That's the build that "Failed", this is where it doesn't make sense for me, the UI is saying "Failed" but the build logs are saying "Success"
^
So those are the build logs for that Failed build, I don't have any logs that display errors which is why I'm confused as to why they were failing as displayed in the UI. I suppose the only other way to actually see the Failures I'm seeing in the UI is to view my project if you don't have any other internal logs?
i can view your project, please link me to the deploy that "failed" the /logs link is not helpfull
Railway
Railway
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
Solution
yep perfect.
looks like you got caught on a box that was having maintenance done on it.
it also looks like every deploy since has not failed, so if you see this again please bring it back up!
Will do! Thanks for taking the time to check it out 😄
Please open your own help thread and provide logs + project id