a year ago
I couldn't find where the second instance of a discord bot was running, and after I removed the active instance and railway said the service wasn't running, the discord bot was still functional and had access to the same environment variables and local network of railway, so an instance somehow didn't get removed properly and was still running, so I fixed it by resetting the discord token, and after it crashed the required amount of times it got removed. I looked through the logs and the deployment that was still running when it shouldn't have been was this
deployment: dcfc8e1d-5546-405d-bfa3-7e8b0dec4980
replica: 42d59944-074a-47e2-beb5-0beec34ccae2
service: 2f5ef2aa-32ce-4023-829a-dca56c961fc9
so maybe that'll help debug it or see what's wrong (this only happened once so far)
here's my project id: 6a89db13-76ce-48a5-952a-110e78307ea5
3 Replies
oh, maybe there was more than one, cuz the different logs for that error have a different deployment/replica id
there's only one replica for this service, and when I reset the token to stop them all of these errored at the same time
deployment: 1e7133a6-f979-47bc-8db2-55ad6ae87226
replica: e349cd2f-add7-49a3-8e2e-01b1d993718d
service: 2f5ef2aa-32ce-4023-829a-dca56c961fc9
deployment: b3f510dd-2f57-44b2-a29d-620a277f3fad
replica: 751f6930-bdcb-4543-a93d-a32b50cb799c
service: 2f5ef2aa-32ce-4023-829a-dca56c961fc9
deployment: dcfc8e1d-5546-405d-bfa3-7e8b0dec4980
replica: 42d59944-074a-47e2-beb5-0beec34ccae2
service: 2f5ef2aa-32ce-4023-829a-dca56c961fc9
a year ago
yeah I've seen this a few times lately, phantom containers, will escalate just incase this is helpful
a year ago
!t
a year ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response brody • about 1 year ago
a year ago
We've identified the containers you're referring to. Our records the containers were shut down a couple of hours ago. Can you confirm whether you still see activity from them?
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
I have a similar problem. I deleted the deploy and all services, but my bot is still running.
replica:07ac9bbd-9c53-4803-a62e-51c751ad06a2
deployment:b1c87a4c-62ee-4cd6-a37d-54f30369a148
Status changed to Solved brody • about 1 year ago