going to need more context on those logs, I don't really know what to make of them

@cybershizo

I can’t look sooner than 30 minutes but I thought I would put it out there in case someone had something similar going on

I think it would help to explain what those logs represent, for both me anyone who looks at that screenshot

I will, but for the meantime they keep coming in. It’s probably not an isolated incident but we’ll see. Give me like 30 minutes to an hour

we just had this incident -

but i would need the service id of the service those logs are referring to in order to check if your deploy was on that host

https://railway.app/project/f0e6a269-403d-4af5-b52f-28a053963dbf/service/4a8253c7-3588-486b-a310-41f59701b673?id=7c4acc9c-05ae-4ddb-8f16-4a62c7687c8a#deploy

Logs started erring here https://railway.app/project/f0e6a269-403d-4af5-b52f-28a053963dbf/logs?filter=%40deployment%3A7c4acc9c-05ae-4ddb-8f16-4a62c7687c8a+-%40replica%3A8cee30b3-d562-4705-9951-ad1fb523015c&context=2024-10-18T20%3A51%3A59.817054000Z

It's working again now, it's likely this incident. Resolved itself automatically

From Oct 18 13:51:59 to Oct 18 14:19:59

yeah your workload would have likely been on that restarted host

It's all good I just figured it was something going on with Railway. Something like this seems to happen every other month or so

Not a big deal just calling it out in case it was affecting others

thank you! we appreciate that, and for what it's worth this was just more GCP instabilities, so we are well underway getting metal ready for production workloads!

Sounds good, thanks

Are you officially a Railway team member now?

I am!

Congrats! Sounds good

Thanks

thank you!!