mirror of
https://github.com/ZJDoc/GitGuide.git
synced 2026-07-15 16:50:12 +08:00
357 lines
12 KiB
Markdown
357 lines
12 KiB
Markdown
|
||
# ERROR
|
||
|
||
## 问题一：GitLab容器一直重启
|
||
|
||
|
||
使用`docker logs`命令查询
|
||
|
||
```
|
||
$ docker log CONTAINER_ID
|
||
...
|
||
...
|
||
System Info:
|
||
------------
|
||
chef_version=14.13.11
|
||
platform=ubuntu
|
||
platform_version=16.04
|
||
ruby=ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]
|
||
program_name=/opt/gitlab/embedded/bin/chef-client
|
||
executable=/opt/gitlab/embedded/bin/chef-client
|
||
|
||
|
||
Running handlers:
|
||
There was an error running gitlab-ctl reconfigure:
|
||
|
||
/etc/gitlab/gitlab.rb:1: unexpected fraction part after numeric literal
|
||
external_url = 192.168.0.144:7002
|
||
^~~~~~~
|
||
/etc/gitlab/gitlab.rb:1: syntax error, unexpected tINTEGER, expecting end-of-input
|
||
external_url = 192.168.0.144:7002
|
||
^~~
|
||
|
||
Running handlers complete
|
||
Chef Client failed. 0 resources updated in 01 seconds
|
||
```
|
||
|
||
发现是`external_url`配置失误导致。解决方法如下：
|
||
|
||
1. 停止`gitlab`容器
|
||
2. 修改配置文件（在主机中）`/srv/gitlab/config/gitlab.rb`
|
||
3. 重新启动容器
|
||
|
||
## 问题二：GitLab导致8080端口冲突
|
||
|
||
### 问题复现
|
||
|
||
安装完`GitLab`后，修改配置文件`/etc/gitlab/gitlab.rb`
|
||
|
||
```
|
||
##external_url 'http://gitlab.example.com'
|
||
external_url 'http://localhost:8800'
|
||
```
|
||
|
||
本以为这样就能修改`GitLab`端口号为`8800`了，没想到再次登录`8080`仍旧出现了`GitLab`页面
|
||
|
||
|
||
|
||
### 问题解析
|
||
|
||
查询哪个程序监听了`8080`端口
|
||
|
||
```
|
||
# netstat -lnp | grep 8080
|
||
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 26436/config.ru
|
||
```
|
||
|
||
查询相应的进程
|
||
|
||
```
|
||
# netstat -lnp | grep 26436
|
||
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 26436/config.ru
|
||
unix 2 [ ACC ] STREAM LISTENING 343538 26436/config.ru /var/opt/gitlab/gitlab-rails/sockets/gitlab.socket
|
||
```
|
||
|
||
仍然是`GitLab`在监听`8080`端口，参考[gitlab 8.13 80 8080端口冲突问题](https://blog.csdn.net/vbaspdelphi/article/details/52979836)，查看配置文件`unicorn.rb`
|
||
|
||
```
|
||
# This file is managed by gitlab-ctl. Manual changes will be
|
||
# erased! To change the contents below, edit /etc/gitlab/gitlab.rb
|
||
# and run `sudo gitlab-ctl reconfigure`.
|
||
|
||
# What ports/sockets to listen on, and what options for them.
|
||
listen "127.0.0.1:8080", :tcp_nopush => true
|
||
```
|
||
|
||
默认情况下`unicorn`同样监听`8080`端口，查询`/etc/gitlab/gitlab.rb`中相应的设置
|
||
|
||
```
|
||
# cat gitlab.rb | grep unicorn
|
||
#unicorn['port'] = 8800
|
||
```
|
||
|
||
### 解决方案
|
||
|
||
需要在`gitlab.rb`上同时修改`unicorn`监听端口号，修改配置文件`/etc/gitlab/gitlab.rb`如下
|
||
|
||
```
|
||
##external_url 'http://gitlab.example.com'
|
||
external_url 'http://localhost:8800'
|
||
unicorn['port'] = 8801
|
||
```
|
||
|
||
重新启动`GitLab`
|
||
|
||
```
|
||
# gitlab-ctl reconfigure
|
||
# gitlab-ctl restart
|
||
```
|
||
|
||
查询配置文件`/var/opt/gitlab/gitlab-rails/etc/unicorn.rb`
|
||
|
||
```
|
||
# cat unicorn.rb | grep listen
|
||
# What ports/sockets to listen on, and what options for them.
|
||
listen "127.0.0.1:8801", :tcp_nopush => true
|
||
```
|
||
|
||
测试端口号
|
||
|
||
```
|
||
$ curl localhost:8080
|
||
curl: (7) Failed to connect to localhost port 8080: Connection refused
|
||
$ curl localhost:8800
|
||
<!DOCTYPE html>
|
||
<html>
|
||
<head>
|
||
<meta content="width=device-width, initial-scale=1, maximum-scale=1" name="viewport">
|
||
...
|
||
...
|
||
# curl localhost:8801
|
||
<html><body>You are being <a href="http://localhost:8801/users/sign_in">redirected</a>.</body></html>
|
||
```
|
||
|
||
## 问题三： [GitLab][Webhook]不允许本地连接
|
||
|
||
在`gitlab`仓库中设置`Webhook`，使用本地连接出现如下错误:
|
||
|
||
```
|
||
Url is blocked: Requests to the local network are not allowed
|
||
```
|
||
|
||
参考:[gitlab使用webhook向jenkins发送请求，报错 Requests to the local network are not allowed](https://blog.csdn.net/xukangkang1hao/article/details/80756085)
|
||
|
||
登录`root`账户，点击`Configure Gitlab`选项
|
||
|
||
|
||
|
||
进入`Settings -> Network`，展开`Outbound requests`，选中`Allow requests to the local network from web hooks and services`
|
||
|
||
|
||
|
||
## 问题四：GitLab: You are not allowed to force push code to a protected branch on this project
|
||
|
||
强制上传代码到`Gitlab`仓库的`dev`分支出错，提示如下：
|
||
|
||
```
|
||
GitLab: You are not allowed to force push code to a protected branch on this project
|
||
```
|
||
|
||
参考：[解决 GitLab: You are not allowed to force push code to a protected branch on this project问题](https://blog.csdn.net/mqdxiaoxiao/article/details/95794053)
|
||
|
||
是由于分支保护的原因，需要进入仓库`setting -> Repository -> Protected Branches`
|
||
|
||
|
||
|
||
允许`dev`分支能够强制推送
|
||
|
||
## 问题五：unicorn出错
|
||
|
||
### 问题描述
|
||
|
||
通过`docker`部署`gitlab`一段时间后，突然出现`502`错误
|
||
|
||
查看容器状态，显示不健康
|
||
|
||
```
|
||
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
||
89481faa2ed1 gitlab/gitlab-ce:latest "/assets/wrapper" 2 weeks ago Up 7 hours (unhealthy)
|
||
```
|
||
|
||
浏览容器日志，发现如下错误：
|
||
|
||
```
|
||
==> /var/log/gitlab/unicorn/unicorn_stdout.log <==
|
||
bundler: failed to load command: unicorn (/opt/gitlab/embedded/bin/unicorn)
|
||
|
||
==> /var/log/gitlab/unicorn/unicorn_stderr.log <==
|
||
ArgumentError: Already running on PID:460 (or pid=/opt/gitlab/var/unicorn/unicorn.pid is stale)
|
||
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:205:in `pid='
|
||
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:137:in `start'
|
||
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/unicorn-5.4.1/bin/unicorn:126:in `<top (required)>'
|
||
/opt/gitlab/embedded/bin/unicorn:23:in `load'
|
||
/opt/gitlab/embedded/bin/unicorn:23:in `<top (required)>'
|
||
|
||
==> /var/log/gitlab/unicorn/current <==
|
||
2019-12-18_12:27:47.34406 failed to start a new unicorn master
|
||
2019-12-18_12:27:47.35882 starting new unicorn master
|
||
2019-12-18_12:27:47.91735 master failed to start, check stderr log for details
|
||
```
|
||
|
||
### 问题解析
|
||
|
||
看样子是`unicorn`的问题，参考：
|
||
|
||
[gitlab服务器502恢复过程](https://blog.csdn.net/zhouchuan152/article/details/95871798)
|
||
|
||
[gitlab docker Web界面打开反应迟钝的解决办法](https://blog.csdn.net/happyfreeangel/article/details/88653846)
|
||
|
||
进入容器内部，查看`unicorn`状态
|
||
|
||
```
|
||
$ docker exec -it xxxx bash
|
||
# gitlab-ctl tail unicorn
|
||
```
|
||
|
||
发现每次`unicorn`显示的`PID`都不同，修改`/etc/gitlab/gitlab.rb`，添加
|
||
|
||
```
|
||
unicorn['listen'] = 'localhost'
|
||
unicorn['port'] = 8999
|
||
```
|
||
|
||
更新并重启后，`gitlab`服务恢复正常
|
||
|
||
```
|
||
# gitlab-ctl reconfigure
|
||
# gitlab-ctl restart
|
||
```
|
||
|
||
## 问题六：版本更新后database出错
|
||
|
||
### 问题描述
|
||
|
||
拉取了最新的`Docker Gitlab`镜像，部署时发现了如下错误：
|
||
|
||
```
|
||
gitlab | System Info:
|
||
gitlab | ------------
|
||
gitlab | chef_version=14.14.29
|
||
gitlab | platform=ubuntu
|
||
gitlab | platform_version=16.04
|
||
gitlab | ruby=ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-linux]
|
||
gitlab | program_name=/opt/gitlab/embedded/bin/chef-client
|
||
gitlab | executable=/opt/gitlab/embedded/bin/chef-client
|
||
gitlab |
|
||
gitlab |
|
||
gitlab | Running handlers:
|
||
gitlab | There was an error running gitlab-ctl reconfigure:
|
||
gitlab |
|
||
gitlab | bash[migrate gitlab-rails database] (gitlab::database_migrations line 55) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
|
||
gitlab | ---- Begin output of "bash" "/tmp/chef-script20200618-23-sfpkhu" ----
|
||
gitlab | STDOUT: rake aborted!
|
||
gitlab | PG::ConnectionBad: could not connect to server: No such file or directory
|
||
gitlab | Is the server running locally and accepting
|
||
gitlab | connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"?
|
||
gitlab | /opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:48:in `block (3 levels) in <top (required)>'
|
||
gitlab | /opt/gitlab/embedded/bin/bundle:23:in `load'
|
||
gitlab | /opt/gitlab/embedded/bin/bundle:23:in `<main>'
|
||
gitlab | Tasks: TOP => gitlab:db:configure
|
||
gitlab | (See full trace by running task with --trace)
|
||
gitlab | STDERR:
|
||
gitlab | ---- End output of "bash" "/tmp/chef-script20200618-23-sfpkhu" ----
|
||
gitlab | Ran "bash" "/tmp/chef-script20200618-23-sfpkhu" returned 1
|
||
```
|
||
|
||
### 问题解决
|
||
|
||
在网上查了一些资料，说是新旧版本的配置格式不一致，需要删除之前的配置数据。幸好在本地保存了之前使用的镜像，打包该镜像后上传到服务器重新加载即可
|
||
|
||
## 问题七：Prometheus吃磁盘空间
|
||
|
||
|
||
在云服务器上部署`Gitlab`，今天发现无法登录了。登上云服务器后发现磁盘容量没有了，通过查找发现`Prometheus`目录下占据了`30GB`的空间（总共`50GB`）
|
||
|
||
参考：
|
||
|
||
[Monitoring GitLab with Prometheus](https://docs.gitlab.com/ee/administration/monitoring/prometheus/)
|
||
|
||
[Prometheus eats disk space in /var/opt/gitlab/prometheus/data](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/4166)
|
||
|
||
[GitLab 官方镜像内部集成 Prometheus 历史数据过大的问题处理](https://lakelight.net/2020/03/24/GitLab-Prometheus-clean.html)
|
||
|
||
`Prometheus`是一个监控服务，会保存历史监控数据，下面尝试关闭该服务并删除之前的数据（在`Docker Gitlab`上操作）
|
||
|
||
1. 修改配置文件`/srv/gitlab/config/gitlab.rb`，添加
|
||
|
||
```
|
||
prometheus_monitoring['enable'] = false
|
||
```
|
||
|
||
2. 关闭`gitlab`并删除`/srv/gitlab/data/prometheus`文件夹数据
|
||
|
||
3. 重启`gitlab`，问题解决
|
||
|
||
## 问题八：Access deined: You do not have permission push to this repository
|
||
|
||
在gitee上新建了一个账户，在上面新建一个仓库，将其ssh链接设置到本地已存在的仓库上，想要把本地仓库推送到远程仓库，出现如下错误：
|
||
|
||
```
|
||
$ git push origin master
|
||
Access deined: You do not have permission push to this repository
|
||
fatal: 无法读取远程仓库。
|
||
|
||
请确认您有正确的访问权限并且仓库存在。
|
||
```
|
||
|
||
其原因在于本地新建了两个`ssh`密钥，设置在`gitee`的不同账户上，ssh使用之前的密钥读取gitee远程仓库，导致出错。参考[如何使用特定的SSH Key提交GIT](https://www.jianshu.com/p/82aa1678411e)
|
||
|
||
在`~/.ssh/config`文件上添加如下内容
|
||
|
||
```
|
||
Host gitee.com
|
||
HostName gitee.com
|
||
User git
|
||
IdentityFile 私钥文件路径
|
||
IdentitiesOnly yes
|
||
```
|
||
|
||
重新提交即可
|
||
|
||
## 问题九：代码库大小限制
|
||
|
||
### 问题描述
|
||
|
||
上传代码到`Gitee`时，打印出如下日志：
|
||
|
||
```
|
||
git push --force git@gitee.com:xx.xx.git master
|
||
remote: Powered by [01;33mGITEE.COM [0m[[01;35mGNK-3.8[0m][0m
|
||
remote: Recommended to reduce the repository size
|
||
remote: This repository(including wiki) size [01;33m581.64 MB[0m exceeds [01;33m500.00 MB[0m
|
||
remote: HelpLink: https://gitee.com/help/articles/4232
|
||
To gitee.com:zjZSTU/xx.xxx.git
|
||
```
|
||
|
||
在网上查询发现是因为单个仓库大小超出了限制（`500MB`），经过一番查询发现`Gitee`和`Coding`的个人仓库都限制在`500MB`，`Github`对单个仓库大小的限制为`1GB`。
|
||
|
||
### 问题解决
|
||
|
||
阿里云的单个仓库限制为`2GB`，能够满足当前需求。
|
||
|
||
各个远程`Git`仓库服务器的官网地址如下：
|
||
|
||
1. [Gitee](https://gitee.com/)
|
||
2. [Coding](https://coding.net/)
|
||
3. [Github](https://github.com/)
|
||
4. [Aliyun Code](https://code.aliyun.com)
|
||
|
||
### 相关阅读
|
||
|
||
* [Gitee 仓库体积过大，如何减小？ ](https://gitee.com/help/articles/4232#article-header0)
|
||
|
||
* [Tencent 仓库大小限制吗？](https://cloud.tencent.com/developer/ask/197652)
|
||
|
||
* [GitHub File and repository size limitations](https://help.github.com/en/github/managing-large-files/what-is-my-disk-quota#file-and-repository-size-limitations)
|
||
|
||
* [Aliyun代码库对文件大小是否有限制？](https://help.aliyun.com/document_detail/153791.html?spm=5176.11065259.1996646101.searchclickresult.30c1183bbCmNS7) |