GitLab部分错误处理记录

gitlab 从13升级到14版本时因为从unicorn替换成了puma。所以要在配置文件中注释所有unicorn相关的配置再进行升级,否则会升级失败

gitlab更新时遇到权限问题,执行如下命令

# 容器部署
docker exec -it gitlab update-permissions

# 软件包部署


GitLab CI/CD流水线作业执行后莫名卡住不动

原因是在/etc/profile中增加了script命令-记录终端交互会话过程来记录用户操作痕迹,去掉该配置即可


临时禁用两步验证

当root用户因为某些原因导致两步验证无法正常使用时,可以通过临时禁用两步验证

gitlab-rails console # 执行完命令后要等一会儿才会进入

# 依次执行下面三行,root可修改为其它指定用户
user = User.find_by_username('root')
user.two_factor_enabled?
user.disable_two_factor!

GitLab所在服务器如果时间不准,飘向过去或未来,都会导致两步验证无法正常工作。

论坛发帖链接

页面错误信息如下

500: We're sorry, something went wrong on our end

Request ID: 01J9P20SGP91HV03ZA2312MCRR

Try refreshing the page, or going back and attempting the action again.

Please contact your GitLab administrator if this problem persists.

程序错误日志如下


2024-10-08_11:35:52.30460 ERROR: no partition of relation "audit_events" found for row

2024-10-08_11:35:52.30461 DETAIL: Partition key of the failing row contains (created_at) = (2024-10-08 11:35:52.299554).

2024-10-08_11:35:52.30462 STATEMENT: /*application:web,correlation_id:01J9NYM1NYD8XATQJ7X8V7EDGP,endpoint_id:SessionsController#create,db_config_name:main*/ INSERT INTO "audit_events" ("author_id", "entity_id", "entity_type", "details", "author_name", "target_details", "created_at", "target_type", "target_id") VALUES (1, 1, 'User', '---

2024-10-08_11:35:52.30463 :with: two-factor

2024-10-08_11:35:52.30463 :target_id: 1

2024-10-08_11:35:52.30464 :target_type: User

2024-10-08_11:35:52.30464 :target_details: Administrator

2024-10-08_11:35:52.30464 :author_name: Administrator

2024-10-08_11:35:52.30464 ', 'Administrator', 'Administrator', '2024-10-08 11:35:52.299554', 'User', 1) RETURNING "id"

解决方案,不要手动调整时间,用ntpd等类似的时间服务器自动同步修正时间即可。不过自动修正时间可能需要很久,可以临时使用上面的“禁用两步验证”方法来登录。

最后更新于