selfhosted runner version 2.278.0 can't be picked

Describe the bug the selfhosted runner can not pick up a job

To Reproduce Steps to reproduce the behavior:

1. install a runner version 2.278.0
2. run a job on this runner
3. the job can’t be picked by this runner

Expected behavior A clear and concise description of what you expected to happen.

Runner Version and Platform

2.278

OS of the machine running the runner? OSX/Windows/Linux/… Linux

What’s not working?

Jan 12 15:49:52 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: √ Connected to GitHub
Jan 12 15:49:54 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Current runner version: '2.285.1'
Jan 12 15:49:54 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: 2022-01-12 07:49:54Z: Listening for Jobs
Jan 12 16:14:54 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner update in progress, do not shutdown runner.
Jan 12 16:14:54 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Downloading 2.286.0 runner
Jan 12 16:50:28 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: An error occurred: Runner package '/root/actions-runner/_work/_update/runner1.tar.g
Jan 12 16:50:28 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner listener exited with error code 2
Jan 12 16:50:28 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner listener exit with retryable error, re-launch runner in 5 seconds.
Jan 12 16:50:33 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Starting Runner listener with startup type: service
Jan 12 16:50:33 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Started listener process, pid: 22965
Jan 12 16:50:35 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: √ Connected to GitHub
Jan 12 16:50:37 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Current runner version: '2.285.1'
Jan 12 16:50:37 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: 2022-01-12 08:50:37Z: Listening for Jobs
Jan 12 17:07:47 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner update in progress, do not shutdown runner.
Jan 12 17:07:48 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Downloading 2.286.0 runner
Jan 12 17:11:06 ip-172-31-45-111.cn-northwest-1.compute.internal systemd[1]: Stopping GitHub Actions Runner (juzibot.test-deploy)...

Job Log Output

Jan 12 19:11:51 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[30232]: Downloading 2.286.0 runner

Runner and Worker’s Diagnostic Logs

If applicable, add relevant diagnostic log information. Logs are located in the runner’s _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.

journalctl -u actions.runner.juzibot.test-deploy.service --since ‘2022-01-12 03:57:49’

Jan 12 15:12:08 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: √ Connected to GitHub Jan 12 15:12:10 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Current runner version: ‘2.285.1’ Jan 12 15:12:10 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: 2022-01-12 07:12:10Z: Listening for Jobs Jan 12 15:22:01 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner update in progress, do not shutdown runner. Jan 12 15:22:02 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Downloading 2.286.0 runner Jan 12 15:49:45 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: An error occurred: Runner package '/root/actions-runner/_work/_update/runner1.tar.g Jan 12 15:49:45 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner listener exited with error code 2 Jan 12 15:49:45 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner listener exit with retryable error, re-launch runner in 5 seconds. Jan 12 15:49:50 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Starting Runner listener with startup type: service Jan 12 15:49:50 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Started listener process, pid: 2081 Jan 12 15:49:52 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: √ Connected to GitHub Jan 12 15:49:54 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Current runner version: ‘2.285.1’ Jan 12 15:49:54 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: 2022-01-12 07:49:54Z: Listening for Jobs Jan 12 16:14:54 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner update in progress, do not shutdown runner. Jan 12 16:14:54 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Downloading 2.286.0 runner Jan 12 16:50:28 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: An error occurred: Runner package '/root/actions-runner/_work/_update/runner1.tar.g Jan 12 16:50:28 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner listener exited with error code 2 Jan 12 16:50:28 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner listener exit with retryable error, re-launch runner in 5 seconds. Jan 12 16:50:33 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Starting Runner listener with startup type: service Jan 12 16:50:33 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Started listener process, pid: 22965 Jan 12 16:50:35 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: √ Connected to GitHub Jan 12 16:50:37 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Current runner version: ‘2.285.1’ Jan 12 16:50:37 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: 2022-01-12 08:50:37Z: Listening for Jobs Jan 12 17:07:47 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Runner update in progress, do not shutdown runner. Jan 12 17:07:48 ip-172-31-45-111.cn-northwest-1.compute.internal runsvc.sh[3366]: Downloading 2.286.0 runner Jan 12 17:11:06 ip-172-31-45-111.cn-northwest-1.compute.internal systemd[1]: Stopping GitHub Actions Runner (juzibot.test-deploy)…

[stardustman]

ok, thanks a lot.

[nikola-jokic]

As of now, no. You would have to manually update your runner. The runner normally receives an update notification on a workflow event. Runner requires the service to send the information needed for the self-update. If you feel like it would be helpful to add this functionality, please post your feedback on the GitHub Feedback site which is actively monitored. Using the forum ensures that we route your problem to the correct team.