GitLab维护笔记

发布于 2025-02-07 07:05:55 字数 126 浏览 0 评论 0原文

我运行了一个GitLab服务器,要安装跑步者。但是,当我注册跑步者时,他们失败了。在“可选维护说明”步骤中,我按Enter跳过该步骤,然后遇到一个错误,然后退出注册会话。

我将如何工作?还是至少是为了跳过这一步骤而不会失败?

I have a GitLab server running and want to install runners. However, when I get to registering the runners they fail. On the "optional maintenance note" step, I press enter to skip that step and I get an error and then it quits the registering session.

How would I get that to work? Or at least so that I can skip that step without failing?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

属性 2025-02-14 07:05:55

这不是维护说明失败。维护注意事项后,跑步者使用Git-Lab服务器注册。失败的是Git-Lab服务器本身上的缓存错误。

运行这些命令以清除这些命令:

gitlab-rails dbconsole --database main
UPDATE projects SET runners_token = null, runners_token_encrypted = null;
UPDATE namespaces SET runners_token = null, runners_token_encrypted = null;
UPDATE application_settings SET encrypted_ci_jwt_signing_key = null;
UPDATE ci_runners SET token = null, token_encrypted = null;
exit

It was not the maintenance notes failing. After the maintenance notes, the runner registers with the git-lab server. What was failing was a cache error on the git-lab server itself.

Run these commands to clear those:

gitlab-rails dbconsole --database main
UPDATE projects SET runners_token = null, runners_token_encrypted = null;
UPDATE namespaces SET runners_token = null, runners_token_encrypted = null;
UPDATE application_settings SET encrypted_ci_jwt_signing_key = null;
UPDATE ci_runners SET token = null, token_encrypted = null;
exit
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文