429 error when runner try to connect to gitlab.com

GitLab CI/CD
1

Hello

After a long period of good working, my runner stop work with an error printed below.

I dont create “Too many Requests”.
I try to register another runner / start runner on different machine (with different IP),
but the error is the same.

How can I bring my runner back to working state?

Thank ypu

logs:

e[37;1mDialing: tcp gitlab.com:443 … e[0;m
e[0;33mWARNING: Checking for builds… failed e[0;m e[0;33mrunnere[0;m=d5c10fbf e[0;33mstatuse[0;m=429 Too Many Requests
e[37;1mDialing: tcp gitlab.com:443 … e[0;m
e[0;33mWARNING: Checking for builds… failed e[0;m e[0;33mrunnere[0;m=a713042f e[0;33mstatuse[0;m=429 Too Many Requests
e[37;1mFeeding runners to channel e[0;m e[37;1mbuildse[0;m=0
e[37;1mDialing: tcp gitlab.com:443 … e[0;m
e[0;33mWARNING: Checking for builds… failed e[0;m e[0;33mrunnere[0;m=d5c10fbf e[0;33mstatuse[0;m=429 Too Many Requests
e[37;1mDialing: tcp gitlab.com:443 … e[0;m
e[0;33mWARNING: Checking for builds… failed e[0;m e[0;33mrunnere[0;m=a713042f e[0;33mstatuse[0;m=429 Too Many Requests

2

We are experiencing the same problem:

● gitlab-runner.service - GitLab Runner
   Loaded: loaded (/etc/systemd/system/gitlab-runner.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2016-10-03 09:48:35 ICT; 52min ago
 Main PID: 1087 (gitlab-ci-multi)
    Tasks: 10
   Memory: 32.0M
      CPU: 55.264s
   CGroup: /system.slice/gitlab-runner.service
           └─1087 /usr/bin/gitlab-ci-multi-runner run --working-directory /home/gitlab-runner --config /etc/gitlab-runner/config.toml --service gitlab-runner --syslog --user gitlab-runner

Oct 03 10:40:42 mongodb62 gitlab-runner[1087]: time="2016-10-03T10:40:42+07:00" level=warning msg="Checking for builds... failed" runner=0fd215d4 status="429 Too Many Requests" 
                                               <nil>
Oct 03 10:40:42 mongodb62 gitlab-ci-multi-runner[1087]: time="2016-10-03T10:40:42+07:00" level=warning msg="Checking for builds... failed" runner=0fd215d4 status="429 Too Many Requests"
Oct 03 10:40:43 mongodb62 gitlab-runner[1087]: time="2016-10-03T10:40:43+07:00" level=warning msg="Checking for builds... failed" runner=6f484b2c status="429 Too Many Requests" 
                                               <nil>
Oct 03 10:40:43 mongodb62 gitlab-ci-multi-runner[1087]: time="2016-10-03T10:40:43+07:00" level=warning msg="Checking for builds... failed" runner=6f484b2c status="429 Too Many Requests"
Oct 03 10:40:44 mongodb62 gitlab-runner[1087]: time="2016-10-03T10:40:44+07:00" level=warning msg="Checking for builds... failed" runner=6694b807 status="429 Too Many Requests" 
                                               <nil>
Oct 03 10:40:44 mongodb62 gitlab-ci-multi-runner[1087]: time="2016-10-03T10:40:44+07:00" level=warning msg="Checking for builds... failed" runner=6694b807 status="429 Too Many Requests"
Oct 03 10:40:45 mongodb62 gitlab-runner[1087]: time="2016-10-03T10:40:45+07:00" level=warning msg="Checking for builds... failed" runner=c1e706f1 status="429 Too Many Requests" 
                                               <nil>
Oct 03 10:40:45 mongodb62 gitlab-ci-multi-runner[1087]: time="2016-10-03T10:40:45+07:00" level=warning msg="Checking for builds... failed" runner=c1e706f1 status="429 Too Many Requests"
Oct 03 10:40:46 mongodb62 gitlab-runner[1087]: time="2016-10-03T10:40:46+07:00" level=warning msg="Checking for builds... failed" runner=0fd215d4 status="429 Too Many Requests" 
                                               <nil>
Oct 03 10:40:46 mongodb62 gitlab-ci-multi-runner[1087]: time="2016-10-03T10:40:46+07:00" level=warning msg="Checking for builds... failed" runner=0fd215d4 status="429 Too Many Requests"
3

I’m having the exact same probleme.

``● gitlab-runner.service - GitLab Runner
Loaded: loaded (/etc/systemd/system/gitlab-runner.service; enabled; vendor preset: disabled)
Active: active (running) since lun. 2016-10-03 19:03:53 CEST; 24min ago
Main PID: 10553 (gitlab-ci-multi)
CGroup: /system.slice/gitlab-runner.service
└─10553 /usr/bin/gitlab-ci-multi-runner run --working-directory /home/gitlab-runner --config /etc/gitlab-runner/config.toml --service gitlab-runner --syslog --user gitlab-runner

oct. 03 19:27:55 62.210.192.109 gitlab-runner[10553]: time=“2016-10-03T19:27:55+02:00” level=warning msg=“Checking for builds… failed” runner=12bed50e status=“429 Too Many Requests”

oct. 03 19:27:55 62.210.192.109 gitlab-ci-multi-runner[10553]: time=“2016-10-03T19:27:55+02:00” level=warning msg=“Checking for builds… failed” runner=12bed50e status=“429 Too Many Requests”
oct. 03 19:27:56 62.210.192.109 gitlab-runner[10553]: time=“2016-10-03T19:27:56+02:00” level=warning msg=“Checking for builds… failed” runner=6025fb9d status=“429 Too Many Requests”

oct. 03 19:27:56 62.210.192.109 gitlab-ci-multi-runner[10553]: time=“2016-10-03T19:27:56+02:00” level=warning msg=“Checking for builds… failed” runner=6025fb9d status=“429 Too Many Requests”
oct. 03 19:27:56 62.210.192.109 gitlab-runner[10553]: time=“2016-10-03T19:27:56+02:00” level=warning msg=“Checking for builds… failed” runner=64038d09 status=“429 Too Many Requests”

oct. 03 19:27:56 62.210.192.109 gitlab-ci-multi-runner[10553]: time=“2016-10-03T19:27:56+02:00” level=warning msg=“Checking for builds… failed” runner=64038d09 status=“429 Too Many Requests”
oct. 03 19:27:57 62.210.192.109 gitlab-runner[10553]: time=“2016-10-03T19:27:57+02:00” level=warning msg=“Checking for builds… failed” runner=6b21b0c6 status=“429 Too Many Requests”

oct. 03 19:27:57 62.210.192.109 gitlab-ci-multi-runner[10553]: time=“2016-10-03T19:27:57+02:00” level=warning msg=“Checking for builds… failed” runner=6b21b0c6 status=“429 Too Many Requests”
oct. 03 19:27:58 62.210.192.109 gitlab-runner[10553]: time=“2016-10-03T19:27:58+02:00” level=warning msg=“Checking for builds… failed” runner=12bed50e status=“429 Too Many Requests”

oct. 03 19:27:58 62.210.192.109 gitlab-ci-multi-runner[10553]: time=“2016-10-03T19:27:58+02:00” level=warning msg=“Checking for builds… failed” runner=12bed50e status=“429 Too Many Requests”
Hint: Some lines were ellipsized, use -l to show in full.``

4

Same problem here. After period of working fine, the same warning shows up all builds are not working:(
Anyone have an idea how to workaround?

5

Same here. Maybe Gitlab servers are being flooded?

6

Looks like that. Need to change “check_interval” in /etc/gitlab-runner/config.toml: