Deployment crashed, but no logs to help troubleshoot
I deployed my code to a staging container, everything worked fine. I merged my code to
main and deployed. The Railway container on production crashed, but there's no logs. As far as I can tell, the code works fine on my local and in the staging environment.8 Replies
Project ID:
34108dc5-7795-469f-b853-2863bbedfa6f34108dc5-7795-469f-b853-2863bbedfa6f
I redeployed an old container, in the meantime, but I don't know how to fix the issue without some good ol'fashioned log data
Can close this. It took 10 minutes for the log data to show up ðŸ˜
yeah theres been ongoing logging issues
Is there any place where we can see some information about the log issues ? That's basically impacting everything from deploys to services logs :/
its not been officially recognized yet
Yeah logging issues everywhere for me, build logs not showing up, service logs delayed or in the worse cases just dropped completely.
@Brody Logs are really spotty. I just deployed new code 15 minutes ago (12:27PM). No logs in Railway UI until 12:34pm, and thats when the log timestamps started, I couldn't view any records prior to 12:34pm. 5 minutes later, I could see log data back to 12:31pm. But new log data isn't showing up... it's 12:42 and the last log record I can see is from 12:36
I'm trying to troubleshoot a live issue, this is pretty challenging
I know, but there's nothing I can do right now, the team isn't online
this has now been fixed