Skip to content

Add link to continue the runner registration process if you leave mid-flow

We'd love your feedback to understand why it didn't work!

There's not much to record since I've already run the script Miguel shared (and so now have runners visible) but, from what I remember, here's what I tried:

  1. I tried using the "create runner" button on the empty state in admin > runners.
  2. I got to the stage where I was setting everything up in my terminal, and I think it created a runner but, I entered "ssh" instead of "shell" as the executor.
  3. I realized that was probably a mistake, so I exited out of the registration process without completing it, with the hope that I could re-run it again, and use the "shell" option instead.
  4. Unfortunately, a runner had been initiated but not registered and, since there was that existing runner, it was trying to delete the unregistered runner, but it couldn't. After that, for any gitlab-runner command I tried, I got error messages, such as the following:
 ERROR: Verifying runner... is removed
 PANIC: Failed to verify the runner. You may be having network problems.`

and

ERROR: Registering runner... forbidden (check registration token) 
PANIC: Failed to register the runner.
  1. Since it seemed like there was a runner (though unregistered), I tried just to run it, but got the following errors:
ERROR: Failed to load config stat /Users/ameliabauerly/.gitlab-runner/config.toml: no such file or directory  builds=0
ERROR: Failed to load config stat /Users/ameliabauerly/.gitlab-runner/config.toml: no such file or directory  builds=0
ERROR: Failed to load config stat /Users/ameliabauerly/.gitlab-runner/config.toml: no such file or directory  builds=0
ERROR: Failed to load config stat /Users/ameliabauerly/.gitlab-runner/config.toml: no such file or directory  builds=0
^CWARNING: [runWait] received stop signal             builds=0 stop-signal=interrupt
WARNING: Graceful shutdown not finished properly    builds=0 error=received stop signal: interrupt
WARNING: Starting forceful shutdown                 StopSignal=interrupt builds=0
FATAL: Failed to start gitlab-runner: "launchctl" failed with stderr: Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.

That's when I asked for help 😅 I have no idea what all of the errors mean or how to fix them. But, I assume that if I had not exited the original registration flow, it probably would have worked just fine. Suspect it's user error here 😆 But, hope that helps!

Edited by Gina Doyle