我用gitlab.com
托管我的存储库,并在DigitalOcean
中安装runner
。它运行良好,直到今天16March2019 14:24泰国时间。
# gitlab-runner status
Runtime platform arch=amd64 os=linux pid=16937 revision=4745a6f3 version=11.8.0
gitlab-runner: Service is running!
# gitlab-runner unregister --all-runners
Runtime platform arch=amd64 os=linux pid=16299 revision=4745a6f3 version=11.8.0
Running in system-mode.
WARNING: Unregistering all runners
ERROR: Unregistering runner from GitLab forbidden runner=2bcd7af4
ERROR: Failed to unregister runner HerrRunner
# gitlab-runner list
Runtime platform arch=amd64 os=linux pid=16346 revision=4745a6f3 version=11.8.0
Listing configured runners ConfigFile=/etc/gitlab-runner/config.toml
HerrRunner Executor=shell Token=2bcd7af455f866ede7991992a68780 URL=https://gitlab.com/
# gitlab-runner --debug run
Runtime platform arch=amd64 os=linux pid=16395 revision=4745a6f3 version=11.8.0
Starting multi-runner from /etc/gitlab-runner/config.toml ... builds=0
Checking runtime mode GOOS=linux uid=0
Running in system-mode.
Configuration loaded builds=0
listenaddress: ""
sessionserver:
listenaddress: ""
advertiseaddress: ""
sessiontimeout: 1800
metricsserveraddress: ""
concurrent: 1
checkinterval: 0
loglevel: null
logformat: null
user: ""
runners:
- name: HerrRunner
limit: 0
outputlimit: 0
requestconcurrency: 0
runnercredentials:
url: https://gitlab.com/
token: 2bcd7af455f866ede7991992a68780
tlscafile: ""
tlscertfile: ""
tlskeyfile: ""
runnersettings:
executor: shell
buildsdir: ""
cachedir: ""
cloneurl: ""
environment: []
preclonescript: ""
prebuildscript: ""
postbuildscript: ""
shell: ""
ssh: null
docker: null
parallels: null
virtualbox: null
cache:
type: ""
path: ""
shared: false
s3: null
gcs: null
s3cachepath: ""
cacheshared: false
serveraddress: ""
accesskey: ""
secretkey: ""
bucketname: ""
bucketlocation: ""
insecure: false
machine: null
kubernetes: null
sentrydsn: null
modtime: 2018-08-12T18:07:07.963445119Z
loaded: true
builds=0
Waiting for stop signal builds=0
Listen address not defined, metrics server disabled builds=0
Listen address not defined, session server disabled builds=0
Starting worker builds=0 worker=0
Feeding runners to channel builds=0
Dialing: tcp gitlab.com:443 ...
ERROR: Checking for jobs... forbidden runner=2bcd7af4
Feeding runners to channel builds=0
ERROR: Checking for jobs... forbidden runner=2bcd7af4
Feeding runners to channel builds=0
ERROR: Checking for jobs... forbidden runner=2bcd7af4
ERROR: Runner https://gitlab.com/2bcd7af455f866ede7991992a68780 is not healthy and will be disabled!
Feeding runners to channel builds=0
Feeding runners to channel builds=0
Feeding runners to channel builds=0
^CWARNING: Requested service stop: interrupt builds=0
All workers stopped. Can exit now builds=0
最终目标
让我的跑者站起来再跑一次
问题:
not healthy
是什么意思?
1.我无法注销我的跑步者。如何解决这个问题?
4条答案
按热度按时间pw9qyyiw1#
当我遇到这种情况时(因为没有sudo访问权限而在用户模式下运行),删除和重新注册runner似乎没有帮助。额外需要的步骤是删除
config.toml
文件(对我来说位于~/.gitlab-runner/config.toml
)。删除该文件后,我能够注册和运行一个新的runner(使用与以前完全相同的命令),一切似乎都很好。注:
当你注册一个runner的时候,它应该是
Configuration (with the authentication token) was saved in "<some/path/config.toml>"
这样的东西,这就是需要删除的文件。zrfyljdw2#
不知道。但是看起来
gitlab.com
删除了我的runner令牌。因此我必须删除我的runner,注册,然后再次运行它。cyvaqqii3#
这是我第一次整合我的runner,任何熟悉gitlab的人都知道这绝不是一件容易的事,我花了很多时间追踪这个错误信息,却发现我完全搞错了方向。
我现在相信我的跑步者告诉我,www.example.com上的“跑步者”gitlab.com不健康,已经被(我的跑步者)拒绝了。当我让它运行并放入管道作业时,它处理得很好,在我的终点没有问题,我花了几个小时什么也没找到!
quhf5bfb4#
我也遇到过同样的问题。按照安装说明中的描述注册你的runner。转到
admin/runners
并单击Show runner installation instructions
按钮。最重要的是Register runner
会话,在那里你必须运行register
命令来解决所描述的问题。例如,linux:按照指示去做,你就可以走了。
一旦你的runner被设置和运行,你可以添加修改到配置文件,停止并在配置更改后再次启动它。
你可能会发现重复的
[[runners]]
部分,如果你尝试自己配置它,然后用register
命令,就会发生这种情况。没关系,只留下一个最新的。