-
Notifications
You must be signed in to change notification settings - Fork 967
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
2 year old runner has randomly broken, Jobs not being picked up #3526
Comments
Very strangely, exactly a week later (as of 30 minutes ago) Jobs have started being picked up again! 🤷♂️ |
Adding to this to keep a log, may be useful if anyone else faces these issues;
After this, no commands would allow the server to reconnect and it would only throw the following error
specifically Removing |
Describe the bug
A suspected recent update has stopped runners from picking up jobs on production but a carbon copy staging environment still works. These servers have been running without any configuration changes for the previous 2 years, no associated software updates have aligned with this issue starting.
All jobs submitted are stuck in
Waiting for a runner to pick up this job...
until they finally time out.The runner is seen successfully polling for Jobs, and the GitHub dashboard shows it as being online and idle, however, GitHub is not releasing jobs to the worker.
The runner updated itself on the 4th, however, issues have only arisen since the 19th at 02:00 UTC
We've attempted restarting the service, and fully rebooting the system, neither result in jobs being picked up.
To Reproduce
It is unknown how to reproduce this broken state.
Expected behavior
Runners should be picking up jobs from GitHub.
Runner Version and Platform
2.320.0
Ubuntu 20.04.6 LTS
This may be a similar issue to #3515, though, Thiers appears to eventually pick up jobs.
The text was updated successfully, but these errors were encountered: