run: gitlab-exporter: (pid 1119) 1309s; run: log: (pid 1116) 1309s run: gitlab-kas: (pid 1133) 1309s; run: log: (pid 1125) 1309s run: gitlab-workhorse: (pid 1121) 1309s; run: log: (pid 1114) 1309s run: logrotate: (pid 1135) 1309s; run: log: (pid 1126) 1309s run...
一、问题描述 我是基于docker搭建的gitlab,docker ps查看gitlab运行状态没有问题,也能够访问gitlab页面。但是查看仓库详情(代码)的时候报错:500 Whoops,something went wrong on our end 二、问题定位 1、进入容器内部 dockerexec-it gitlab bash 2、查看gitlab的运行状态 gitlab-ctl status 发现有组件没有启动,...
这个问题困扰了我很久,第一次遇到时没有管,国为只有用管理员操作admin area的setting才会出现,一般用户没有影响,当时就没有管它,现在有个东西要用管理员设定才行,必须要解决了。 百度里基本上都没有有效信息,最终按gitlab社区的一个方法解决了。记录如下: 首先sudo gitlab-rails c进入gitalab的控制台,然后依次...
权限不够
gitlab正常显示登录页面 登录用户(或创建删除project)报错报500错误 “Whoops, something went wrong on our end.” 查找日志: 查看/var/log/gitlab/gitlab-rails/production.log,发现报错对应如下日志: StartedGET"/-/metrics"for127.0.0.1at2020-06-1810:11:59+0800Processing by MetricsController#index as ...
删除project失败，报500错误 “Whoops, something went wrong on our end.”查找 /var/log/gitlab/gitlab-rails/production.log ，对比执行过程，发现报错对应如下日志： OpenSSL::Cipher::CipherError ():https://gitlab.com/gitlab-org/gitlab-foss/-/issues/66002 https://gitlab.com/...
500 Whoops, something went wrong on our end. /etc/gitlab/gitlab.rb配置错误,例如redis未配置,数据库未配置 502-Whoops, GitLab is taking too much time to respond 端口被占用 超时时间太短 正在启动 常用命令 查看版本 cat /opt/gitlab/embedded/service/gitlab-rails/VERSION ...
1. 页面显示500,Whoops, something went wrong on our end. 500Whoops, something went wrong on ourend. Try refreshing the page, or going backandattempting the action again. Please contact your GitLab administratorifthis problem persists. 如何检查和定位问题?
Whoops, something went wrong on our end. Try refreshing the page, or going back and attempting the action again. Please contact your GitLab administrator if this problem persists. 如何检查和定位问题? 使用命令检查所有服务的状态 1 sudo gitlab-ctl status 检查服务状态如下 1 2 3 4 5 6 7 run...
For each webhook, all event test are ok EXCEPT for the merge request event test which leads to an error 500 code page “Whoops, something went wrong on our end.” from Gitlab. This is happening now, after the last Gitlab …