Skip to content

`Checking for builds ... forbidden runner=PzqH8kzY` when started by `gitlab-ci-multi-runner run`

Checking for builds ... forbidden when started by command ./gitlab-ci-multi-runner run

As described in title.

Proposal

  1. Open this project in Gogland and set client.skipVerify to true for local https connection;
  2. It claims Checking for builds ... forbidden when it is started;
  3. Retry to start it in terminal and it claims with same information;

None

usermba:gitlab-ci-multi-runner user$ ./gitlab-ci-multi-runner run
Starting multi-runner from /Users/user/.gitlab-runner/config.toml ...  builds=0
WARNING: Running in user-mode.                     
WARNING: Use sudo for system-mode:                 
WARNING: $ sudo gitlab-runner...                   
                                                   
Configuration loaded                                builds=0
Metrics server disabled                            
ERROR: Checking for builds... forbidden             runner=PzqH8kzY
ERROR: Checking for builds... forbidden             runner=PzqH8kzY
ERROR: Checking for builds... forbidden             runner=PzqH8kzY
ERROR: Runner https://10.130.3.5/ci<TOKEN> is not healthy and will be disabled! 
^CAll workers stopped. Can exit now                   builds=0
WARNING: Requested service stop: interrupt          builds=0

Register will be ok

./gitlab-ci-multi-runner register

This will start to register new runner to local GitLab instance with same url and token specified in /Users/user/.gitlab-runner/config.toml and it turns out working great. The GitLab instance also shows the new runner.

Please have a look at this and any advice would be appreicate.