Runner reusage is disabled

Question

Runner reusage is disabled

SteveBox0 opened this issue 2 years ago · comments

Very recently a new issue has started when creating a runner with the same name after removing the old container from the host. This was not an issue a day ago.

Runner reusage is disabled
Obtaining the token of the runner
Configuring

A runner exists with the same name *******.
An error occurred: Not configured. Run config.(sh/cmd) to configure the runner.

myoung34 · Answer 1 · Tue Sep 13 2022 22:48:14 GMT+0800 (China Standard Time)

What's your runtime configuration look like

SteveBox0 · Answer 2 · Tue Sep 13 2022 22:52:08 GMT+0800 (China Standard Time)

docker stop github-runner-EXAMPLENAME
docker rm github-runner-EXAMPLENAME
docker pull myoung34/github-runner:latest

docker run --rm -d --name github-runner-EXAMPLENAME -e RUNNER_NAME="github-runner-EXAMPLENAME" -e ACCESS_TOKEN="**************" -e LABELS="github-runner-EXAMPLENAME" -e RUNNER_SCOPE="org" -e ORG_NAME="*************" -e RUNNER_WORKDIR="/tmp/github-runner-your-repo" --dns="1.0.0.1" --dns="1.1.1.1" myoung34/github-runner:latest

myoung34 · Answer 3 · Wed Sep 14 2022 00:25:28 GMT+0800 (China Standard Time)

Interesting. Looks like something between

2.296.1:

A runner exists with the same name
√ Successfully replaced the runner
√ Runner connection is good

and 2.296.2:

A runner exists with the same name
A runner exists with the same name github-runner-EXAMPLENAME.
An error occurred: Not configured. Run config.(sh/cmd) to configure the runner.

Digging in to see if I caused it or if tthe upstream project changed

myoung34 · Answer 4 · Wed Sep 14 2022 00:50:34 GMT+0800 (China Standard Time)

@SteveBox0 this is a bug from runner 2.296.2

Filed a bug here

SteveBox0 · Answer 5 · Thu Sep 15 2022 12:32:04 GMT+0800 (China Standard Time)

Seems the workaround using 2.296.1 docker image is no longer working as its force updating to 2.296.2.

Current runner version: '2.296.1'
2022-09-15 04:29:48Z: Listening for Jobs
Runner update in progress, do not shutdown runner.
Downloading 2.296.2 runner

myoung34 · Answer 6 · Thu Sep 15 2022 12:49:11 GMT+0800 (China Standard Time)

The wiki details how to disable updates

James Stocker · Answer 7 · Thu Sep 15 2022 14:57:19 GMT+0800 (China Standard Time)

I have also been caught by this issue, runners had stopped working, I set up an env file with:

DISABLE_AUTO_UPDATE=1

Set and updated my script to use the --env-file and pin to the 2.296.1 release of the runner and it all works again

Roman Makarov · Answer 8 · Thu Sep 29 2022 16:54:02 GMT+0800 (China Standard Time)

For me it also works to remove runners manually via GH UI. (organization -> settings -> runners). I have to do it from time to time(around once per 2 weeks).

Dave Tapley · Answer 9 · Tue Oct 18 2022 07:04:08 GMT+0800 (China Standard Time)

So I am also seeing Runner reusage is disabled, but then the run just exits after √ Settings Saved., same issue or different? 🤔

myoung34 · Answer 10 · Tue Oct 18 2022 07:05:07 GMT+0800 (China Standard Time)

Can you post all the logs from startup?

Dave Tapley · Answer 11 · Thu Oct 20 2022 01:56:02 GMT+0800 (China Standard Time)

@myoung34 sure! Is there a verbosity setting somewhere? Not much to see but posted below in case helps.

I get a new offline runner in https://github.com/organizations/JEFuller/settings/actions/runners each time I try to start.

This had been working fine for months, but older image won't start now due to:

#252

Thanks 🙏🏻

dave@lededje:~$ docker run --rm -e RUNNER_SCOPE="org" -e ORG_NAME=jefuller -e LABELS=vision -e ACCESS_TOKEN='XXX' -v /var/run/docker.sock:/var/run/docker.sock -v /_work:/_work --name github-runner --entrypoint /entrypoint.sh myoung34/github-runner:2.298.2
Runner reusage is disabled
Obtaining the token of the runner
Configuring

--------------------------------------------------------------------------------
|        ____ _ _   _   _       _          _        _   _                      |
|       / ___(_) |_| | | |_   _| |__      / \   ___| |_(_) ___  _ __  ___      |
|      | |  _| | __| |_| | | | | '_ \    / _ \ / __| __| |/ _ \| '_ \/ __|     |
|      | |_| | | |_|  _  | |_| | |_) |  / ___ \ (__| |_| | (_) | | | \__ \     |
|       \____|_|\__|_| |_|\__,_|_.__/  /_/   \_\___|\__|_|\___/|_| |_|___/     |
|                                                                              |
|                       Self-hosted runner registration                        |
|                                                                              |
--------------------------------------------------------------------------------

# Authentication


√ Connected to GitHub

# Runner Registration




√ Runner successfully added
√ Runner connection is good

# Runner settings


√ Settings Saved.

dave@lededje:~$

Dave Tapley · Answer 12 · Thu Oct 20 2022 07:48:46 GMT+0800 (China Standard Time)

@myoung34 Runner reusage is disabled turned out to be unrelated, moved to #253

SteveBox0 · Answer 13 · Thu Oct 20 2022 19:13:20 GMT+0800 (China Standard Time)

@myoung34 As its taking a while to get an official fix. Would it be worth while adding a small curl command to your startup process to delete the existing running?

myoung34 · Answer 14 · Thu Oct 20 2022 21:21:43 GMT+0800 (China Standard Time)

I think before that I'd like to see if we can get some comment from the actions team before I start shimming in hacks

myoung34 · Answer 15 · Thu Oct 20 2022 22:16:18 GMT+0800 (China Standard Time)

@SteveBox0 @davetapley It looks as though this might have been hotfixed upstream without release notes

Can you retest?

# Authentication


√ Connected to GitHub

# Runner Registration




A runner exists with the same name
√ Successfully replaced the runner
√ Runner connection is good

# Runner settings


√ Settings Saved.


√ Connected to GitHub

Current runner version: '2.296.2'
2022-10-20 14:14:29Z: Listening for Jobs

James Stocker · Answer 16 · Thu Oct 20 2022 22:32:34 GMT+0800 (China Standard Time)

I updated to latest recently and haven't seen the same issue since, I think you're right about upstream fix

…

On Thu, 20 Oct 2022, 16:16 myoung34, ***@***.***> wrote: @SteveBox0 <https://github.com/SteveBox0> @davetapley <https://github.com/davetapley> It looks as though this might have been hotfixed upstream without release notes Can you retest? # Authentication √ Connected to GitHub # Runner Registration A runner exists with the same name √ Successfully replaced the runner √ Runner connection is good # Runner settings √ Settings Saved. √ Connected to GitHub Current runner version: '2.296.2' 2022-10-20 14:14:29Z: Listening for Jobs — Reply to this email directly, view it on GitHub <#243 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB626UV5OEY5Y7IMFXACOU3WEFH33ANCNFSM6AAAAAAQLQRQ7M> . You are receiving this because you commented.Message ID: ***@***.***>

Dave Tapley · Answer 17 · Fri Oct 21 2022 02:18:36 GMT+0800 (China Standard Time)

@myoung34 should I be doing something to update first? I'm still seeing the same, and to be double sure, for me "the same" means that I am seeing Runner reusage is disabled immediately after docker run (i.e. before the snippet you posted).

dave@lededje:~$ docker run --rm -e RUNNER_SCOPE="org" -e ORG_NAME=jefuller -e LABELS=vision -e ACCESS_TOKEN='XXX' -v /var/run/docker.sock:/var/run/docker.sock -v /_work:/_work --name github-runner myoung34/github-runner:2.298.2
Runner reusage is disabled
Obtaining the token of the runner
Configuring

--------------------------------------------------------------------------------
|        ____ _ _   _   _       _          _        _   _                      |
|       / ___(_) |_| | | |_   _| |__      / \   ___| |_(_) ___  _ __  ___      |
|      | |  _| | __| |_| | | | | '_ \    / _ \ / __| __| |/ _ \| '_ \/ __|     |
|      | |_| | | |_|  _  | |_| | |_) |  / ___ \ (__| |_| | (_) | | | \__ \     |
|       \____|_|\__|_| |_|\__,_|_.__/  /_/   \_\___|\__|_|\___/|_| |_|___/     |
|                                                                              |
|                       Self-hosted runner registration                        |
|                                                                              |
--------------------------------------------------------------------------------

# Authentication


√ Connected to GitHub

# Runner Registration




√ Runner successfully added
√ Runner connection is good

# Runner settings


√ Settings Saved.


√ Connected to GitHub

Current runner version: '2.298.2'
2022-10-20 18:17:16Z: Listening for Jobs

myoung34 · Answer 18 · Mon Oct 24 2022 08:36:51 GMT+0800 (China Standard Time)

If you want to use that, you need to set the CONFIGURED_ACTIONS_RUNNER_FILES_DIR var per the README. relevant code is here

Runner reusage is disabled does not mean it wont replace, it means that the data directory will attempt to be preserved across container runs

myoung34 · Answer 19 · Tue Oct 25 2022 21:33:15 GMT+0800 (China Standard Time)

Closing for now as it seems like the original issue is resolved. Let me know if thats not the case