Ephemeral JIT runner hangs after "Acknowledging runner request" and never exits; job fails with "lost communication" (2.338.0, linux-x64)

オープン
#4,855 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
42/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
csharp, github
領域
ci-cd, devops

調査の方向性

Start with the runner listener logs and the request acknowledgement and credential token flow described in the report; compare the related issues #4309 and #2040 for clues. The report has no reproducer or named source files, so first trace where the listener waits after acknowledging a request and look for a way to reproduce the hang. Done means the runner starts the worker or exits cleanly when it cannot acquire the job.

索引モデルが issue の本文から書いたものです。

説明

Describe the bug

A runner registered with a JIT config (ephemeral, one job) accepts a job and then hangs. The listener's diag log ends at "Acknowledging runner request" and one token-request line. Nothing follows, and no Runner.Worker process is started. In the case we traced, GitHub failed the job about 10 minutes later with "The self-hosted runner lost communication with the server", and the registration was gone afterwards (GET /orgs/{org}/actions/runners/{id} returned 404).

The listener process never exits. It stays alive with 13 threads, its main thread in futex_wait and its TCP connections open, so the service manager never restarts it. Two runners on the same host hung this way about an hour apart. Each stayed hung for 6–7 hours, until we killed it.

To reproduce

We can't reproduce it on demand. Both cases had these conditions:

  • Runner 2.338.0, linux-x64, Ubuntu 24.04, kernel 6.8.
  • Registered via generate-jitconfig. .runner has "ephemeral": true and "disableUpdate": true. Started through runsvc.sh under systemd, one job per start.
  • The job request arrived within about a second of "Listening for Jobs".
  • The runner directory is read-only to the runner user, except _work and _diag. In normal operation this causes only the expected "Read-only file system: .credentials" error after a completed job. Hundreds of jobs a day complete normally on this host.
Expected behavior

The job runs. Or, if the listener cannot acquire it, the listener gives up and exits so the supervisor can restart it.

Runner version / OS

2.338.0, Ubuntu 24.04.4 LTS x86_64

Logs

The listener diag log, last lines. Both instances end the same way:

[17:35:23Z INFO BrokerMessageListener] Session created.
[17:35:23Z INFO Terminal] WRITE LINE: Current runner version: '2.338.0'
[17:35:23Z INFO Terminal] WRITE LINE: 2026-11-11 17:35:23Z: Listening for Jobs
[17:35:23Z INFO JobDispatcher] Set runner/worker IPC timeout to 30 seconds.
[17:35:23Z INFO BrokerMessageListener] Acknowledging runner request '<id>'.
[17:35:23Z INFO CredentialManager] Creating credential type: OAuth
[17:35:23Z INFO RSAFileKeyManager] Loading RSA key parameters from file <runner>/.credentials_rsaparams
[17:35:23Z INFO GitHubActionsService] AAD Correlation ID for this token request: Unknown

Nothing follows these lines, and there is no Worker log.

Job annotation: "The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. ..."

Possibly related: #4309, #2040.

主要言語
C#
スター
6.4k
フォーク
1.5k
平均マージ
1日 7時間
マージ済み PR(30日)
36

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

actions/runner のほかの issue

actions/runner の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。