We’re using self-hosted runners in our organization and it’s working fine. What I want to do now is use bigger instances and run multiple runners per host.
I have a script that uses a PAT to generate a runner token, and then uses that token to start a runner. When I run the script multiple times on the same host, only one will register correctly. I get errors like:
A session for this runner already exists. 2020-09-03 19:26:14Z: Runner connect error: The actions runner 94e9c2e0ca90995c7764c845 already has an active session for owner ip-20-10-43-71.. Retrying until reconnected.
Cannot configure the runner because it is already configured. To reconfigure the runner, run 'config.cmd remove' or './config.sh remove' first.
I have noticed that the token I get from the token registration endpoint is the same for each runner I try to launch. While this might be the issue, I see no way to “force” the generation of a new registration token.
I should also mention using a different (randomly-generated)
--workdir when I run