Penultimate version of runner is deprecated (Runner version v2.320.0 is deprecated and cannot receive messages)

[ilyaibraev]

Describe the bug An error occurs when using runner version 2.230.0.

This version is the second to last and I have not found any information about plans to make it deprecated. Is this expected behavior?

To Reproduce Steps to reproduce the behavior:

1. Configure using ./config.sh with --disableupdate
2. ./run.sh

Expected behavior Works without errors

Runner Version and Platform

2.320.0 x64 linux (ubuntu 18)

What's not working?

Current runner version: '2.320.0'
2025-01-13 04:31:47Z: Listening for Jobs
An error occured: Runner version v2.320.0 is deprecated and cannot receive messages.
Runner listener exit with terminated error, stop the service, no retry needed.
Exiting runner...

Job Log Output

Runner and Worker's Diagnostic Logs

Runner_20250113-091656-utc.log

[edbighead]

https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners#controlling-runner-software-updates-on-self-hosted-runners

Any updates released for the software, including major, minor or patch releases, are considered as an available update. If you do not perform a software update within 30 days, the GitHub Actions service will not queue jobs to your runner. In addition, if a critical security update is required, the GitHub Actions service will not queue jobs to your runner until it has been updated.

[biswajitm2024]

Current runner version: '2.321.0' I am facing same issues like this : https://github.com/actions/runner/issues/3501

[pietervdheijden]

I've a similar issue:

[RUNNER 2025-01-13 14:48:02Z ERR Terminal] WRITE ERROR: An error occured: Runner version v2.320.0 is deprecated and cannot receive messages. An error occured: Runner version v2.320.0 is deprecated and cannot receive messages. [RUNNER 2025-01-13 14:48:02Z ERR Listener] GitHub.DistributedTask.WebApi.AccessDeniedException: Runner version v2.320.0 is deprecated and cannot receive messages. [RUNNER 2025-01-13 14:48:02Z ERR Listener] at GitHub.Actions.RunService.WebApi.BrokerHttpClient.GetRunnerMessageAsync(Nullable1 sessionId, String runnerVersion, Nullable1 status, String os, String architecture, Nullable1 disableUpdate, CancellationToken cancellationToken) [RUNNER 2025-01-13 14:48:02Z ERR Listener] at GitHub.Runner.Common.BrokerServer.<>c__DisplayClass7_0.<<GetRunnerMessageAsync>b__0>d.MoveNext() [RUNNER 2025-01-13 14:48:02Z ERR Listener] --- End of stack trace from previous location --- [RUNNER 2025-01-13 14:48:02Z ERR Listener] at GitHub.Runner.Common.RunnerService.RetryRequest[T](Func1 func, CancellationToken cancellationToken, Int32 maxRetryAttemptsCount, Func`2 shouldRetry) [RUNNER 2025-01-13 14:48:02Z ERR Listener] at GitHub.Runner.Listener.MessageListener.GetNextMessageAsync(CancellationToken token) [RUNNER 2025-01-13 14:48:02Z ERR Listener] at GitHub.Runner.Listener.Runner.RunAsync(RunnerSettings settings, Boolean runOnce) [RUNNER 2025-01-13 14:48:02Z ERR Listener] at GitHub.Runner.Listener.Runner.RunAsync(RunnerSettings settings, Boolean runOnce) [RUNNER 2025-01-13 14:48:02Z ERR Listener] at GitHub.Runner.Listener.Runner.RunAsync(RunnerSettings settings, Boolean runOnce) [RUNNER 2025-01-13 14:48:02Z ERR Listener] at GitHub.Runner.Listener.Runner.ExecuteCommand(CommandSettings command) [RUNNER 2025-01-13 14:48:02Z ERR Listener] at GitHub.Runner.Listener.Program.MainAsync(IHostContext context, String[] args) Runner listener exit with terminated error, stop the service, no retry needed. Exiting runner...

Upgrading to the latest version (v2.321.0) has resolved the issue. However, having to update the solution every 30 days doesn't seem like a sustainable solution moving forward.

[sebkow]

We had the same issues. We bumped our version runners from 2.320.0 > 2.321.0 and jobs started to get picked up. Is it really expected that we update these every month or so? It seems excessive.

[zeemy23]

this hit us, too. is it best to just set the version to latest?

[ilyaibraev]

Of course, it is not a problem to update to the latest version. The only thing is that I had compatibility issues with the latest runner on Ubuntu 18, which is important to me at the moment.

[ywang-psee]

We have encountered the same issue and were forced to update to v2.321.0. However, the latest version has removed node16, which is unacceptable for us! Commit : Remove node16 from the runner.

[sebkow]

We have encountered the same issue and were forced to update to v2.321.0. However, the latest version has removed node16, which is unacceptable for us! Commit : Remove node16 from the runner.

Node 16 has been End-of-Life for some time now.

[anlesk]

We found ourselves in the loop hole where we can not update runner or deploy ARC because both operations runs on self-hosted runners that became suddenly disabled. There should be a way to work around that...

[rr-paras-patel]

We are also facing this issue with multiple runner groups. is that autoupdate got disabled by default ?

[mihma]

Same issue here. Is there a workaround?

[mikehuebner]

Just got this on our self hosted runners

An error occured: Runner version v2.321.0 is deprecated and cannot receive messages.