Gitlab-runner version: 10.1.0
Ubuntu: 16.04
已安装的跑步者
我已根据instructions安装了跑步者,并再次根据instructions注册了跑步者。
问题
因此,跑步者在活动后的5分钟内接受了第一个,一个或两个作业,然后在那个时间之后,所有作业都在该跑步者处待决。
/etc/gitlab-runner/config.toml
:
concurrent = 1
check_interval = 0
[[runners]]
name = "ubuntu-test-runner"
url = "edited-out"
token = "edited-out"
executor = "shell"
[runners.cache]
正在运行sudo service gitlab-runner status
:
gitlab-runner.service - GitLab Runner
Loaded: loaded (/etc/systemd/system/gitlab-runner.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2017-11-09 10:59:44 GMT; 24min ago
Main PID: 7156 (gitlab-runner)
CGroup: /system.slice/gitlab-runner.service
└─7156 /usr/bin/gitlab-runner run --working-directory /home/gitlab-runner --config /etc/gitlab-runner/config.toml --service gitlab-runner --syslog --user gitlab-runner
Nov 09 11:00:12 su[7343]: + ??? root:gitlab-runner
Nov 09 11:00:12 su[7343]: pam_unix(su:session): session opened for user gitlab-runner by (uid=0)
Nov 09 11:00:12 su[7348]: Successful su for gitlab-runner by root
Nov 09 11:00:12 su[7348]: + ??? root:gitlab-runner
Nov 09 11:00:12 su[7348]: pam_unix(su:session): session opened for user gitlab-runner by (uid=0)
Nov 09 11:00:12 su[7352]: Successful su for gitlab-runner by root
Nov 09 11:00:12 su[7352]: + ??? root:gitlab-runner
Nov 09 11:00:12 su[7352]: pam_unix(su:session): session opened for user gitlab-runner by (uid=0)
Nov 09 11:00:44 gitlab-runner[7156]: time="2017-11-09T11:00:44Z" level=warning msg="Appending trace to coordinator aborted" code=202 job=765 job-log=0-846 job-status=canceled runner=28fdac52 sent-log=846-846 status="202 Accepted"
<nil>
Nov 09 11:00:44 gitlab-runner[7156]: time="2017-11-09T11:00:44Z" level=warning msg="Appending trace to coordinator aborted" code=202 job=765 job-log=0-846 job-status=canceled runner=28fdac52 sent-log=846-846 status="202 Accepted"
因此,跑步者服务是活跃的并且正在运行(接受了第一份工作),但似乎没有接受任何更多的工作并且一切都处于待定状态。
我也可以在网站上看到/runners/admin
中的跑步者,但最后一次接触只是继续上升而且没有重置。
如果我运行sudo gitlab-runner restart
,它会再次接收作业,但在第一个作业之后停止接受作业。
有没有其他方法可以调试为什么跑步者不接受更多的工作?或者如果有人知道我有什么问题?
答案 0 :(得分:1)
是的;
停止你的跑步者(gitlab-runner stop
),然后使用debug flag运行附件,这样你就可以看到它所做的一切:
gitlab-runner --debug run
开始为它提供工作。