blocks|key|633674|text|我不知道为什么，但我发现gitlab-runner已经完全失效了。我已经试过修好它了。在第一步，我更新了gitlab-runner位--它没有工作。之后，我决定重新安装gitlab-runner，因此我已经完成了以下步骤：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|633675|使用以下命令行移除gitlab用户：sudo+deluser+--remove-home+gitlab-runner|ordered-list-item|633676|遵循这里上的手动安装和配置。|633677|而且起作用了。|633678|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.gitlab.com/runner/install/linux-manually.html^0|C|D|1G|D|0|I|14|0|2|2|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|I|3|J|5|H|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|K|3|L|5|6|7|16|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

I don't why but I found the <code>gitlab-runner</code> was completely out of service. I've tried to fix it. at the first step, I've updated the <code>gitlab-runner</code> bit it didn't work. after that I decided to reinstall the gitlab-runner so I've met this steps:

<ol>
<li>removing the gitlab-runner user with this command line: <code>sudo deluser --remove-home gitlab-runner</code></li>
<li>following the manual installation and configuration on <a href="https://docs.gitlab.com/runner/install/linux-manually.html" rel="nofollow noreferrer">here</a>.</li>
</ol>

and it worked.

blocks|key|1933225|text|对我来说，以下几点解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1933226|gitlab-runner+restart|code-block|syntax|javascript|1933227|其中gitlab-runner是指向gitlab-ci-multi-runner的符号链接。|offset|length|style|CODE|1933228|GitLab运行程序是一个开源项目，用于运行作业并将结果发送回GitLab。它与GitLab+CI一起使用，这是GitLab中包含的开源持续集成服务，用于协调作业。|blockquote|1933229|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.gitlab.com/runner/commands/README.html^0|0|0|2|D|I|M|I|M|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Z|8|@$I|10|J|11|K|L]|$I|12|J|13|K|L]]|9|@$I|14|J|15|1|16]]|A|$]]|$1|M|3|N|5|O|7|17|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]]]

To me, the following solved the problem:

<pre><code>gitlab-runner restart
</code></pre>

Where <code>gitlab-runner</code> is a symlink to <a href="https://docs.gitlab.com/runner/commands/README.html" rel="noreferrer"><code>gitlab-ci-multi-runner</code></a>:

<blockquote>
 GitLab Runner is the open source project that is used to run your jobs and send the results back to GitLab. It is used in conjunction with GitLab CI, the open-source continuous integration service included with GitLab that coordinates the jobs.
</blockquote>

blocks|key|1933239|text|我也犯了同样的错误，但是在GKE上使用了gitlab+runner。为了解决这个问题，我刚刚删除了gitlab的跑步吊舱。一个新的吊舱被初始化，连接再次启动。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1933240|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same error but using gitlab runner on GKE. To fix it I just deleted the gitlab-runner pod. A new pod was initialized and the connection was up again.

blocks|key|1975603|text|分享我的经验给未来的读者。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1975604|在我的例子中，互联网并没有在安装gitlab的机器上工作。|1975605|我已经修复了我的gitlab跑步机上的互联网问题，一切都如期而至。|1975606|谢谢!|1975607|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Sharing my experience for future readers.

In my case, the internet was not working on the machine in which gitlab-runner was installed.

I have fixed the internet issue on my gitlab-runner's machine and everything works as expected.

Thanks!

blocks|key|1975673|text|如果您的运行是在systemd下运行的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1975674|journalctl+-u+gitlab-runner.service|code-block|syntax|javascript|1975675|可能会有启发作用。在我的案子里是这样的。|1975676|gitlab-runner[18449]:+FATAL:+chdir+/home/gitlab-runner:+no+such+file+or+directory|1975677|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

If you runner is run under systemd

<pre><code>journalctl -u gitlab-runner.service
</code></pre>

may prove enlightening. It did in my case.

<pre><code>gitlab-runner[18449]: FATAL: chdir /home/gitlab-runner: no such file or directory
</code></pre>

blocks|key|1975733|text|重新启动gitlab-runner之后，您可以将其用于新的寄存器运行程序：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1975734|gitlab-runner+restart

gitlab-runner+register+--name+my-runner+--url+http://gitlab.example.com+--registration-token+my-registration-token|code-block|syntax|javascript|1975735|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

after restart gitlab-runner , you can use this for new register runner : 

<pre><code>gitlab-runner restart

gitlab-runner register --name my-runner --url http://gitlab.example.com --registration-token my-registration-token
</code></pre>

blocks|key|633830|text|抱歉让这条旧线复活了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|633831|我目前正在做一个在本地工作的gitlab跑步者。还处于早期阶段，但最终将变得非常重要。似乎gitlab不想要/有时间来做这个，所以给您。https://github.com/firecow/gitlab-runner-local|offset|length|633832|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/firecow/gitlab-runner-local^0|0|1W|1A|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Sorry for resurrecting this old thread. 

I'm currently working on making a gitlab runner that works locally.
Still in the early phases, but eventually it will become very relevant.
It doesn't seem like gitlab want/have time to make this, so here you go.
<a href="https://github.com/firecow/gitlab-runner-local" rel="nofollow noreferrer">https://github.com/firecow/gitlab-runner-local</a>

blocks|key|1975779|text|这对我起了作用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1975780|sudo+gitlab-runner+verify|code-block|syntax|javascript|1975781|因为gitlab-runner+restart实际上没有重新启动运行程序|offset|length|style|CODE|1975782|entityMap^0|0|0|2|L|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

This worked for me:

<pre><code>sudo gitlab-runner verify
</code></pre>

since <code>gitlab-runner restart</code> didn't actually restarted runners

blocks|key|633875|text|使用journalctl+-u+gitlab-runner+-f检查gitlab-runner日志|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|633876|对我来说，问题是：|633877|gitlab-runner[2023]:+FATAL:+Service+run+failed+++++++++++++++++++++++++++error=chdir+/var/lib/gitlab-runner:+no+such+file+or+directory|code-block|syntax|javascript|633878|因此创建了文件夹并重新启动了gitlab。|633879|sudo+mkdir+/var/lib/gitlab-runner
sudo+gitlab-runner+restart|633880|可能与root用户未运行的安装有关。|633881|entityMap^0|2|U|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|11|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

Check gitlab-runner logs with <code>journalctl -u gitlab-runner -f</code>

For me the problem was:

<pre><code>gitlab-runner[2023]: FATAL: Service run failed error=chdir /var/lib/gitlab-runner: no such file or directory
</code></pre>

so created the folder and restarted gitlab-runner 

<pre><code>sudo mkdir /var/lib/gitlab-runner
sudo gitlab-runner restart
</code></pre>

probably something to do with installation not run by root user

blocks|key|1975823|text|对我来说，问题是，我们自己托管的GitLab的网址发生了变化。我必须手动更改跑步者的URL：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1975824|sudo+vi+/etc/gitlab-runner/config.toml|code-block|syntax|javascript|1975825|重新启动后，我可以确认所有跑步者都回到了网上：|1975826|sudo+gitlab-runner+restart
sudo+gitlab-runner+verify|1975827|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

For me the problem was, that the URL of our self-hosted GitLab changed. I had to change the URL of the runners manually:
<pre><code>sudo vi /etc/gitlab-runner/config.toml
</code></pre>
After restarting, I could verify that all runners were back online:
<pre><code>sudo gitlab-runner restart
sudo gitlab-runner verify
</code></pre>

blocks|key|1975856|text|在我的例子中，在一个老gitlab的升级+(9.5.1+->+11.4)之后，我无法让我的跑步者工作。即使在移除它并注册了一个新的。我注意到，我的config.toml文件没有与我的新运行程序的运行程序CI/CD设置页面中的标记匹配的令牌。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1975857|我这样做是为了让它发挥作用：|1975858|删除/etc/gitlab-runner/config.toml文件(可能不必要)|ordered-list-item|1975859|在Gitlab中点击项目的CI/CD设置下的Reset+runners+registration+token，注册一个新的运行程序(gitlab-runner+register)|1975860|一如既往地继续进行跑步者注册。|1975861|在那之后，我的跑步者被抓起来，像往常一样工作。|1975862|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.gitlab.com/runner/install/linux-repository.html#upgrading-to-gitlab-runner-10^0|21|B|I|2|0|0|0|2|U|0|M|W|1U|M|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|F|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|K|3|L|5|J|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|M|3|N|5|J|7|1D|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1E|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

In my case, after <a href="https://docs.gitlab.com/runner/install/linux-repository.html#upgrading-to-gitlab-runner-10" rel="nofollow noreferrer">upgrading</a> from an old gitlab-runner (9.5.1 -&gt; 11.11.4) I couldn't get my runner to work. Even after removing it and registering a new one.
I noticed that my <code>config.toml</code> file didn't have the token that matches the one in the Runner CI/CD Settings page for my new runner.
I did the following to get it to work:
<ol>
<li>Remove the <code>/etc/gitlab-runner/config.toml</code> file (perhaps
unnecessary)
</li>
<li>Click on <code>Reset runners registration token</code> in Gitlab under project's CI/CD Settings -&gt; Runner page while registering a new runner (<code>gitlab-runner register</code>)
</li>
<li>Continue with runner registration as usual.
</li>
</ol>
After that, my runner was picked up and worked as usual.

recently my runners have been stopped and I don't know why?

I've just upgraded <code>nodejs</code> on the server and it did happen.

after this problem, I've tried to update <code>gitlab</code> to the latest version and check the runner status but the problem still persists and in the title of grey icon shows: 

<blockquote>
 Runner is offline, the last contact was about 22 hours ago.
</blockquote>

<a href="https://i.stack.imgur.com/2hBez.png" rel="noreferrer"><img src="https://i.stack.imgur.com/2hBez.png" alt="Runner is offline, the last contact was about 22 hours ago"></a>

What should I do?

and when I try to <code>Retry stuck jobs</code>, see this error:

<blockquote>
 This job is stuck, because you don't have any active runners online with any of these tags assigned to them: 'my label'.
</blockquote>

Any Help is appreciated!

gitlab: Runner is offline, last contact was about some hours ago

最近我的跑步者被叫停了，我不知道为什么？我刚刚升级了服务器上的nodejs，这确实发生了。在发生此问题后，我尝试将gitlab更新为最新版本并检查运行状态，但问题仍然存在，灰色图标的标题显示：跑步者离线了，最后一次接触是在22小时前。​​我该怎么办？当我尝试Retry stuck jobs时，会看到以下错误：这份工作被...

问gitlab:跑步者离线了，最后一次联系是几个小时前
EN

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问gitlab:跑步者离线了，最后一次联系是几个小时前EN