-
Notifications
You must be signed in to change notification settings - Fork 1k
Self hosted runners failing with WRITE ERROR: A session for this runner already exists #3441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @soumik-avoma, do you have a link to a workflow run where this issue is occurring? |
Hi @luketomlinson,
|
👋Hi @soumik-avoma |
This is what we use for registering the runner. We do not call
|
Hi @soumik-avoma please try at least doubling the memory of your runner. |
How can we verify this with logs or other hints? |
We have the same situation in our self hosted runners windows |
Running into the same issue with macOS runners. Action runners keep randomly disappearing from github and if I check the local logs, I see they failed like this a few days before. |
We had a similar issue. We run the ARC in EKS and deleting the pod wasn't helping because we kept seeing that Manually removing the runner (not the runner scale set) helped. After the pod went down, a new one was spawned, a new runner was registered and it started accepting jobs. |
Same issue, subscribed |
We are using self-hosted ephimeral runners for our github jobs. Recently we are seeing jobs failing randomly with the error This job failed on the UI. On further digging we found out that it's trying to run the job on a runner which is already in
Active
state instead ofIdle
. We also saw the following logs.ERR Terminal] WRITE ERROR: A session for this runner already exists
It gets stuck in this process for long and then fails. Ex:
We even tried upgrading the action agent to v2.319.1 , but the issue still persists.
All of our runners have the same labels hence the job could easily pickup any runner in
Idle
state, but instead its trying to pickup a runner which is inActive
state.The text was updated successfully, but these errors were encountered: