Self-hosted runners disappeared
Problem
Associated GitHub Community topic: https://github.community/t/disappearing-self-hosted-runners/137669 The customer has added some self-hosted runners for his repository, but the runners would completely disappear as if he never added any. When he refreshes, the runners would come back. Some would be `Offline` but would go back to being `Idle` after another refresh. Other times when he refreshes the runners disappear again. When the customer logs into the runner machines to check their status, he can see a lot of connection retries. [code block]
Error Output
error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Resolve Disappearing Self-Hosted Runners Issue
The issue of disappearing self-hosted runners is likely caused by network connectivity problems between the runners and GitHub's servers. The error message indicates that the HTTP requests are timing out, which can occur due to firewall settings, network instability, or incorrect runner configurations. Additionally, if the runners are not properly registered or if there are issues with the GitHub Actions service, it can lead to the runners appearing offline or disappearing altogether.
Awaiting Verification
Be the first to verify this fix
- 1
Check Network Configuration
Ensure that the network settings on the self-hosted runner machines allow outbound connections to GitHub's servers. This includes checking firewall rules and proxy settings that might be blocking the connection.
- 2
Verify Runner Configuration
Reconfigure the self-hosted runners to ensure they are correctly set up. This includes verifying the registration token and ensuring that the runner is properly connected to the correct repository.
bashgh runner configure --url https://github.com/OWNER/REPO --token YOUR_TOKEN - 3
Increase Timeout Settings
Modify the runner's configuration to increase the HTTP request timeout settings. This can help mitigate issues with slow network connections.
bashexport GITHUB_RUNNER_TIMEOUT=1200 - 4
Update Runner Software
Ensure that the self-hosted runner software is up to date. Outdated versions may have bugs that could contribute to connectivity issues. Download the latest version from GitHub.
bashcd actions-runner && ./svc.sh stop && ./svc.sh uninstall && ./config.sh --url https://github.com/OWNER/REPO --token YOUR_TOKEN && ./svc.sh install && ./svc.sh start - 5
Monitor Runner Status
After making the changes, monitor the status of the runners in the GitHub Actions settings. Check for any error messages or connection issues that may arise.
Validation
Confirm that the self-hosted runners remain visible and online in the GitHub Actions settings after refreshing the page multiple times. Additionally, check the runner logs for any connection errors or timeouts.
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep