Via the gitlab web interface, I have been adding/deleting runners (specific/group) which are actually running on a Raspberry Pi. In this process it seems like something has been broken in the configuration of the gitlab-runner service which prevents it connecting properly and accepting jobs
I can’t find much information about the logs which are printed on the terminal, but here is a dump from systemctl status girlab-runner
Sep 06 02:29:58 gl-runner-1 gitlab-runner[547]: Starting multi-runner from /etc/gitlab-runner/config.toml… builds=0
Sep 06 02:29:58 gl-runner-1 gitlab-runner[547]: Running in system-mode.
Sep 06 02:29:58 gl-runner-1 gitlab-runner[547]:
Sep 06 02:29:58 gl-runner-1 gitlab-runner[547]: Configuration loaded builds=0
Sep 06 02:29:58 gl-runner-1 gitlab-runner[547]: listen_address not defined, metrics & debug endpoints disabled builds=0
Sep 06 02:29:58 gl-runner-1 gitlab-runner[547]: [session_server].listen_address not defined, session endpoints disabled builds=0
Sep 06 02:30:05 gl-runner-1 gitlab-runner[547]: ERROR: Checking for jobs… forbidden runner=rYtG2F-w
Sep 06 02:30:06 gl-runner-1 gitlab-runner[547]: ERROR: Checking for jobs… forbidden runner=rYtG2F-w
Sep 06 02:30:09 gl-runner-1 gitlab-runner[547]: ERROR: Checking for jobs… forbidden runner=rYtG2F-w
Sep 06 02:30:09 gl-runner-1 gitlab-runner[547]: ERROR: Runner https://gitlab.com/rYtG2F-wfaVGGAmczVFZ is not healthy and will be disabled!
Here is the config file:
concurrent = 1
check_interval = 0
[session_server]
session_timeout = 1800
[[runners]]
name = “gitlab-runner-pi-01”
url = “https://gitlab.com/”
token = “rYtG2F-wfaVGGAmczVFZ”
executor = “shell”
[runners.custom_build_dir]
[runners.cache]
[runners.cache.s3]
[runners.cache.gcs]
[runners.cache.azure]