Gitlab 13.x 升级 14.x

#!/bin/bash

# 检查是否传入了参数
if [ -z "$1" ]; then
    echo "错误: 请提供项目 ID (Project ID)"
    echo "用法: $0 <project_id>"
    exit 1
fi

PROJECT_ID=$1

# 计算 Project ID 的 SHA256 哈希值
# 注意：必须使用 printf "%s" 防止引入换行符导致哈希值错误
HASH=$(printf "%s" "$PROJECT_ID" | sha256sum | awk '{print $1}')

# 提取哈希值的前两位和三四位
DIR1=${HASH:0:2}
DIR2=${HASH:2:2}

# 拼接基础路径
BASE_PATH="@hashed/${DIR1}/${DIR2}/${HASH}"

echo "=========================================="
echo "Project ID : $PROJECT_ID"
echo "SHA256 Hash: $HASH"
echo "=========================================="
echo "🌟 物理服务器磁盘路径 (Git-Data):"
echo "代码仓库 : /var/opt/gitlab/git-data/repositories/${BASE_PATH}.git"
echo "Wiki仓库 : /var/opt/gitlab/git-data/repositories/${BASE_PATH}.wiki.git"
echo "------------------------------------------"
echo "📦 备份压缩包 (.tar) 中的路径:"
echo "代码备份 : repositories/${BASE_PATH}.bundle"
echo "Wiki备份 : repositories/${BASE_PATH}.wiki.bundle"
echo "=========================================="

# 备份完成后，默认会在 /var/opt/gitlab/backups/ 目录下生成一个类似这样的 .tar 压缩包：
1535000000_2018_08_23_11.2.3_gitlab_backup.tar
sudo gitlab-rake gitlab:backup:create

# 重要的文件备份
sudo mkdir -p /root/gitlab-config-backup
sudo cp /etc/gitlab/gitlab.rb /root/gitlab-config-backup/
sudo cp /etc/gitlab/gitlab-secrets.json /root/gitlab-config-backup/

# 定时备份，CRON=1 参数的作用是静默运行，如果没有错误就不会输出乱码信息
0 2 * * * /opt/gitlab/bin/gitlab-rake gitlab:backup:create CRON=1

# Stop the processes that are connected to the database
docker exec -it <name of container> gitlab-ctl stop unicorn
docker exec -it <name of container> gitlab-ctl stop puma
docker exec -it <name of container> gitlab-ctl stop sidekiq

# Verify that the processes are all down before continuing
docker exec -it <name of container> gitlab-ctl status

# Run the restore
docker exec -it <name of container> gitlab-backup restore BACKUP=1535000000_2018_08_23_11.2.3

# Restart the GitLab container
docker restart <name of container>

# Check GitLab
docker exec -it <name of container> gitlab-rake gitlab:check SANITIZE=true

# 查看当前 GitLab 版本
sudo gitlab-rake gitlab:env:info | grep "Version:"

# 检查传统存储项目数量
sudo gitlab-rake gitlab:storage:legacy_projects

# 列出所有传统存储项目
sudo gitlab-rake gitlab:storage:list_legacy_projects

# 检查传统存储附件数量
sudo gitlab-rake gitlab:storage:legacy_attachments

# 进入 Rails 控制台
sudo gitlab-rails console

# 查找所有只读项目
Project.where(repository_read_only: true).each do |project|
  puts "项目ID: #{project.id}, 名称: #{project.name}"
end

# 批量取消只读（需谨慎）
Project.where(repository_read_only: true).update_all(repository_read_only: false)

# 进入 GitLab Rails 控制台
sudo gitlab-rails console

# 查找所有已归档的项目
Project.where(archived: true).each do |project|
  puts "项目ID: #{project.id}, 名称: #{project.name}, 路径: #{project.full_path}"
end

# 批量取消
Project.where(archived: true).update_all(archived: false)

# 遍历所有项目
gitlab-rails runner "Project.all.pluck(:id).each { |id| print id, ' ' }"

# 进入数据库命令行 (PostgreSQL)
sudo gitlab-rails dbconsole

# 在 SQL 命令行中执行：
SELECT id FROM projects;

# 执行迁移
sudo gitlab-rake gitlab:storage:migrate_to_hashed

# 验证迁移结果（应返回 0）
sudo gitlab-rake gitlab:storage:legacy_projects
sudo gitlab-rake gitlab:storage:legacy_attachments

# 进入数据库控制台
sudo gitlab-rails dbconsole

# 清空项目令牌（PostgreSQL）
UPDATE projects SET runners_token = NULL, runners_token_encrypted = NULL;

# 退出数据库并重新迁移
\q
sudo gitlab-rake gitlab:storage:migrate_to_hashed

# 进入容器修复
docker exec -it gitlab bash
chown git:git /var/opt/gitlab/.ssh/authorized_keys
chmod 600 /var/opt/gitlab/.ssh/authorized_keys

#!/bin/bash
# 获取所有项目ID
PROJECT_IDS=$(sudo gitlab-rails runner "puts Project.all.pluck(:id).join(' ')")

for pid in $PROJECT_IDS; do
  echo "验证项目ID: $pid"
  # 检查哈希路径是否存在
  HASH=$(echo -n "$pid" | sha256sum | awk '{print $1}')
  REPO_PATH="/var/opt/gitlab/git-data/repositories/@hashed/${HASH:0:2}/${HASH:2:2}/$HASH"
  if [ -d "$REPO_PATH.git" ]; then
    echo "✓ 仓库存在"
  else
    echo "✗ 仓库缺失"
  fi
done

# 存储完整性检查
sudo gitlab-rake gitlab:storage:check

# 清理孤儿存储（迁移后的遗留空目录）
sudo gitlab-rake gitlab:storage:cleanup

/var/opt/gitlab/git-data/repositories/myteam/backend-api.git

/var/opt/gitlab/git-data/repositories/@hashed/a6/65/a665a45920422f9d417e4867efdc4fb8a04a1f3fff1fa07e998e86f7f7a27ae3.git

1. # 查看当前GitLab版本
2. sudo gitlab-rake gitlab:env:info | grep "Version:"

4. # 检查传统存储项目数量
5. sudo gitlab-rake gitlab:storage:legacy_projects

7. # 列出所有传统存储项目
8. sudo gitlab-rake gitlab:storage:list_legacy_projects

10. # 检查传统存储附件数量
11. sudo gitlab-rake gitlab:storage:legacy_attachments

13. # 查看哈希存储项目数量（如果已经开始迁移）
14. sudo gitlab-rake gitlab:storage:hashed_projects


bash

# 创建完整备份
sudo gitlab-backup create

# 备份文件通常位于/var/opt/gitlab/backups/
# 同时备份配置文件
sudo cp /etc/gitlab/gitlab.rb /etc/gitlab/gitlab.rb.bak
sudo cp /etc/gitlab/gitlab-secrets.json /etc/gitlab/gitlab-secrets.json.bak

# 进入GitLab Rails控制台
sudo gitlab-rails console

# 查找所有只读项目
Project.where(repository_read_only: true).each do |project|
  puts "项目ID: #{project.id}, 名称: #{project.name}, 路径: #{project.full_path}"
end

# 如果需要批量修改（谨慎操作！）
Project.where(repository_read_only: true).update_all(repository_read_only: false)

1. # 第一步：执行迁移
2. sudo gitlab-rake gitlab:storage:migrate_to_hashed

4. # 预期输出示例：
5. # Enqueuing migration of 42 projects in batches of 200. Done!
6. # Background migration scheduled for 42 projects.

8. # 第二步：检查后台迁移状态
9. # 访问GitLab管理后台：Admin -> Monitoring -> Background Jobs
10. # 或使用API检查
11. sudo gitlab-rake db:migrate:status

13. # 第三步：验证迁移结果
14. sudo gitlab-rake gitlab:storage:hashed_projects
15. sudo gitlab-rake gitlab:storage:legacy_projects  # 应该返回0
16. sudo gitlab-rake gitlab:storage:legacy_attachments  # 应该返回0

Enqueuing migration of 41 projects in batches of 200. Done!

# 进入数据库控制台
sudo gitlab-rails dbconsole

# 对于PostgreSQL数据库，执行以下SQL
UPDATE projects SET runners_token = NULL, runners_token_encrypted = NULL;

# 退出数据库
\q

# 重新执行迁移
sudo gitlab-rake gitlab:storage:migrate_to_hashed

# 查看后台迁移队列
sudo gitlab-rake db:migrate:status | grep -i background

# 查看特定迁移的详细信息
sudo gitlab-rails console
BackgroundMigrationWorker.jobs.each do |job|
  puts "Job: #{job['class']}, Args: #{job['args']}, Created: #{Time.at(job['created_at'])}"
end

# 检查数据库锁
sudo gitlab-psql -c "SELECT pid, relation::regclass, mode, granted FROM pg_locks WHERE relation::regclass::text LIKE '%project%';"

1. # 检查磁盘使用情况
2. df -h /var/opt/gitlab

4. # 检查inode使用情况（这个容易被忽略）
5. df -i /var/opt/gitlab

could not open /var/opt/gitlab/.ssh/authorized_keys

1. # 方法一：在docker run命令中设置正确权限
2. docker run -d --name gitlab \
3. --hostname gitlab.example.com \
4. -v /srv/gitlab/config:/etc/gitlab \
5. -v /srv/gitlab/logs:/var/log/gitlab \
6. -v /srv/gitlab/data:/var/opt/gitlab \
7. --privileged=true \  # 关键参数，提升权限
8. gitlab/gitlab-ce:13.12.15-ce.0

10. # 方法二：启动后进入容器修复
11. docker exec -it gitlab bash
12. chown git:git /var/opt/gitlab/.ssh/authorized_keys
13. chmod 600 /var/opt/gitlab/.ssh/authorized_keys

# 在每个Gitaly节点上检查
sudo gitlab-rake gitlab:storage:hashed_projects

#!/bin/bash
# validate_migration.sh

# 获取所有项目ID
PROJECT_IDS=$(sudo gitlab-rails runner "puts Project.all.pluck(:id).join(' ')")

for pid in $PROJECT_IDS; do
  echo "验证项目ID: $pid"

  # 检查项目是否存在
  sudo gitlab-rails runner "p = Project.find_by(id: $pid); puts '项目: ' + p.full_path if p"

  # 检查仓库是否存在
  REPO_PATH="/var/opt/gitlab/git-data/repositories/@hashed/$(echo -n $pid | sha256sum | cut -c1-2)/$(echo -n $pid | sha256sum | cut -c3-4)/$(echo -n $pid | sha256sum)"
  if [ -d "$REPO_PATH.git" ]; then
    echo "✓ 仓库存在: $REPO_PATH"
  else
    echo "✗ 仓库缺失: $pid"
  fi

  # 尝试读取仓库信息
  sudo -u git git --git-dir="$REPO_PATH.git" log --oneline -1 2>/dev/null && echo "✓ 仓库可读" || echo "✗ 仓库不可读"

  echo "---"
done

1. # 测试git clone性能
2. time sudo -u git git clone /var/opt/gitlab/git-data/repositories/@hashed/4a/4a/4a44dc15364204a80fe80e9039455cc1608281820fe2b24f1e5233ade6af1dd5.git /tmp/test-clone

4. # 测试git push性能
5. cd /tmp/test-clone
6. echo "# Test" >> README.md
7. time sudo -u git git add README.md
8. time sudo -u git git commit -m "Test commit"
9. time sudo -u git git push origin master


bash

13.12.15 → 14.0.12 → 14.3.6 → 14.9.5 → 14.10.5

1. # 14.x中推荐的最小配置变更
2. gitlab_rails['gitlab_shell_ssh_port'] = 22
3. gitlab_rails['monitoring_whitelist'] = ['127.0.0.0/8', '::1/128']

5. # 如果使用外部PostgreSQL
6. gitlab_rails['db_adapter'] = 'postgresql'
7. gitlab_rails['db_encoding'] = 'unicode'
8. gitlab_rails['db_host'] = 'postgresql.example.com'
9. gitlab_rails['db_port'] = 5432


ruby

1. # 停止GitLab服务
2. sudo gitlab-ctl stop

4. # 恢复备份（确保有13.12.15环境）
5. sudo gitlab-backup restore BACKUP=timestamp_of_backup

7. # 恢复配置文件
8. sudo cp /etc/gitlab/gitlab.rb.bak /etc/gitlab/gitlab.rb
9. sudo cp /etc/gitlab/gitlab-secrets.json.bak /etc/gitlab/gitlab-secrets.json

11. # 重新配置并启动
12. sudo gitlab-ctl reconfigure
13. sudo gitlab-ctl start


bash

# 在 /etc/gitlab/gitlab.rb 中配置多个存储路径
git_data_dirs({
  "default" => {
    "path" => "/var/opt/gitlab/git-data"
  },
  "storage2" => {
    "path" => "/mnt/storage2/git-data"
  }
})

# Prometheus抓取配置示例
# 注意：GitLab Rails 的 /-/metrics 端点由 Web 服务（Nginx 80/443）暴露，9090 是 Omnibus 内置 Prometheus 本身的端口
scrape_configs:
  - job_name: 'gitlab-rails'
    metrics_path: '/-/metrics'
    static_configs:
      - targets: ['gitlab.example.com'] # 指向 Web 端口（80/443）

# 每月执行一次存储完整性检查
sudo gitlab-rake gitlab:storage:check

# 存储完整性检查（哈希路径由 SHA256 派生，冲突概率可忽略）
sudo gitlab-rake gitlab:storage:check

# 清理孤儿存储（迁移后可能遗留的空目录）
sudo gitlab-rake gitlab:storage:cleanup

migration = Gitlab::Database::BackgroundMigration::BatchedMigration.find_by(
  job_class_name: 'BackfillMissingNamespaceIdOnNotes',
  table_name: 'notes'
)
migration

# 更新 interval 为 120（单位为秒）
migration.update!(interval: 120)

migration.interval：每个批次任务下发的时间间隔（秒）。
migration.batch_size：每个大批次处理的记录数。
migration.sub_batch_size：每个子批次（实际单次 UPDATE/INSERT）处理的记录数。