cicd system_error ai_generated true

Error: The runner 'self-hosted-runner-01' is offline and cannot accept jobs. Ensure the runner is running and connected.

ID: cicd/github-actions-self-hosted-runner-offline

Also available as: JSON · Markdown · 中文
80%Fix Rate
85%Confidence
1Evidence
2023-06-15First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
GitHub Actions runner 2.300.0 active — — —
Ubuntu 22.04 active — — —
Windows Server 2022 active — — —

Root Cause

The self-hosted GitHub Actions runner has lost connection to GitHub due to network issues, stale runner process, or token expiration, preventing job assignment.

generic

中文

自托管的 GitHub Actions 运行器因网络问题、运行器进程过期或令牌过期而失去与 GitHub 的连接，导致无法分配任务。

Official Documentation

https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners

Workarounds

  1. 85% success Run the runner's config script with --replace to regenerate the token and reconnect: ./config.sh remove --token <token> && ./config.sh --url https://github.com/org/repo --token <new_token> 
    Run the runner's config script with --replace to regenerate the token and reconnect: ./config.sh remove --token <token> && ./config.sh --url https://github.com/org/repo --token <new_token>
  2. 75% success Check runner logs at ~/actions-runner/_diag/Runner_*.log for specific errors (e.g., HTTP 401) and fix network or proxy settings accordingly. 
    Check runner logs at ~/actions-runner/_diag/Runner_*.log for specific errors (e.g., HTTP 401) and fix network or proxy settings accordingly.

中文步骤

  1. Run the runner's config script with --replace to regenerate the token and reconnect: ./config.sh remove --token <token> && ./config.sh --url https://github.com/org/repo --token <new_token>
  2. Check runner logs at ~/actions-runner/_diag/Runner_*.log for specific errors (e.g., HTTP 401) and fix network or proxy settings accordingly.

Dead Ends

Common approaches that don't work:

  1. 40% fail

    Restarting the runner service without checking logs may mask underlying issues like token expiry.

  2. 20% fail

    Uninstalling and re-installing the runner is overkill and loses configuration; often a simple reconnect suffices.

  3. 30% fail

    Killing the runner process and restarting may not fix token issues if the runner is not properly re-authenticated.