Too many runners registered #1544
-
|
We're running ARC version Has anyone else faced similar issues, and if so how are you tackling this issue? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 9 replies
-
|
what do your runner manifests look like? Your runners are likely using the |
Beta Was this translation helpful? Give feedback.
-
|
so depending on what |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Very interesting, good to know! That image Is built from runner version |
Beta Was this translation helpful? Give feedback.
-
|
I believe there isn't really a reason not to use latest, I'm not sure how GitHub manage support for runner versions across all the different GHES versions (pretty much most Action features require logic in the actions/runner software in addition to the server-side of things), you'd need to check their docs for what is supported. But basically, always run the latest runner version possible for your GHES environment, there is never really a reason to stick on older versions beyond waiting to see if the new release is bug free. If you are on GHES => 3.3 then you just need to rebuild your container (please do check with GitHub how suppot works first) against latest and you should get the supported |
Beta Was this translation helpful? Give feedback.
-
|
another reason for staying current with the runner version is we've had multiple reports, and apparently GitHub have confirmed, is that the self-update process can cause massive delays in jobs being allocated to runners https://github.com/actions-runner-controller/actions-runner-controller/blob/master/TROUBLESHOOTING.md#delay-in-jobs-being-allocated-to-runners |
Beta Was this translation helpful? Give feedback.
-
|
Hey I have a similar issue, the number of offline runners is growing daily, in my case I am using the default images |
Beta Was this translation helpful? Give feedback.
-
|
Which version of the controller and runner are you using? |
Beta Was this translation helpful? Give feedback.
-
|
I am using version 0.23. I am seeing a steady increase in the number of the offline runners |
Beta Was this translation helpful? Give feedback.
-
|
This seems to have been the root cause. Thank you @toast-gear! I'll add a note to the FAQs/help docs :) |
Beta Was this translation helpful? Give feedback.
-
|
we've actually just removed support for the --once flag entirely so you can't even configure the --once flag anymore (#1196), it's been in the making for a long time. This problem will naturally disappear as people are now required to use GHES => 3.3 to use our runners at all. People running < 3.3 will start to disappear as their ARC system will stop being functional once they upgrade their base image unless they stop using ours as their base which seems like a bad idea and more effort than just upgrading their GHES instance (especially given GitHub will at some point remove support for the flag too) |
Beta Was this translation helpful? Give feedback.
-
|
Good news about this topic. |
Beta Was this translation helpful? Give feedback.
-
|
We're locking this discussion because it has not had recent activity and/or other members have asked for more information to assist you but received no response. Thank you for helping us maintain a productive and tidy community for all our members. |
Beta Was this translation helpful? Give feedback.
what do your runner manifests look like? Your runners are likely using the
--onceflag which doesn't include logic to unregister them, If you are on GHES => 3.3 you can upgrade to latest ARC without any problems which will automatically set the new--ephemeralflag. Note we are removing support fo rthe--onceflag entirely very very very soon #1196 so you will need to use the new flag soon to not have problems