Backup warnings and errors

How to Use GitLab Self-managed
1

Hi,

when I start a backup from command line using gitlab-backup create I get a lof of warnings and errors

time="2021-09-09T09:52:54Z" level=warning msg="skipped backup" error="repository skipped" gl_project_path=ipb/rad relative_path=@hashed/ef/2d/ef2d127de37b942baad06145e54b0c619a1f22327b2ebbcfbec78f5564afe39d.design.git storage_name=default
...
2021-09-09 09:55:46 +0000 -- done
2021-09-09 09:55:46 +0000 -- Dumping uploads ...
2021-09-09 09:55:51 +0000 -- done
2021-09-09 09:55:51 +0000 -- Dumping builds ...
2021-09-09 09:55:51 +0000 -- done
2021-09-09 09:55:51 +0000 -- Dumping artifacts ...
2021-09-09 09:55:52 +0000 -- done
2021-09-09 09:55:52 +0000 -- Dumping pages ...
2021-09-09 09:55:52 +0000 -- done
2021-09-09 09:55:52 +0000 -- Dumping lfs objects ...
2021-09-09 09:55:52 +0000 -- done
2021-09-09 09:55:52 +0000 -- Dumping container registry images ...
2021-09-09 09:55:52 +0000 -- [DISABLED]
Creating backup archive: 1631181352_2021_09_09_14.2.3_gitlab_backup.tar ... done
Uploading backup archive to remote storage  ... skipped
Deleting tmp directories ... done
done
done
done
done
done
done
done
Deleting old backups ... done. (0 removed)

Is this normal?

I’m using gitlab-ce.x86_64-14.2.3-ce.0.el8 (centos 8)

2

Is what normal? There are neither warnings nor errors in that output, it’s simply status messages.

If you haven’t configured GitLab to upload backups to remote storage, it is normal for it to skip it.

In a production environment that has been running for some time, it’s not normal for it not to remove any old backups. But I have a feeling this is a really new setup, in that case there might very well not be any backups that are old enough that the cleanup will delete them.

3

Hi,

I was worried about the error="repository skipped" message.

It’s not a new install, I migrated from version 13.12.9 to 14.0.9, 14.1.5 and finally to 14.2.3

With version 13.12.9 these warnings never appear.

I have GitLab configured to keep the backups of the last 3 days. Backups are stored by default int the /var/opt/gitlab/backups/ directory. The System Administrator makes a daily backup of these.

4

I’m seeing this issue as well after an upgrade to 14 major version (via omnibus package on CentOS 7). All repositories report the repository skipped error and the backup is SIGNIFICANTLY smaller than previous.

5

I am having the same issue. I just transitioned from 12.9.1 to 14.2.4. The following is an excerpt of my backup log:

# gitlab-backup create

2021-09-20 01:12:38 +0000 -- Dumping database ...

Dumping PostgreSQL database gitlabhq_production ... [DONE]

2021-09-20 01:12:52 +0000 -- done

2021-09-20 01:12:52 +0000 -- Dumping repositories ...

time="2021-09-20T01:12:53Z" level=info msg="started backup" gl_project_path=justacec/TemperatureAnalysis relative_path=@hashed/d4/73/d4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35.git storage_name=default

time="2021-09-20T01:12:53Z" level=info msg="started backup" gl_project_path=justacec/TemperatureAnalysis.wiki relative_path=@hashed/d4/73/d4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35.wiki.git storage_name=default

time="2021-09-20T01:12:54Z" level=warning msg="skipped backup" error="repository skipped" gl_project_path=justacec/TemperatureAnalysis.wiki relative_path=@hashed/d4/73/d4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35.wiki.git storage_name=default

time="2021-09-20T01:12:54Z" level=info msg="started backup" gl_project_path=justacec/TemperatureAnalysis relative_path=@hashed/d4/73/d4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35.design.git storage_name=default

time="2021-09-20T01:12:54Z" level=warning msg="skipped backup" error="repository skipped" gl_project_path=justacec/TemperatureAnalysis relative_path=@hashed/d4/73/d4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35.design.git storage_name=default

time="2021-09-20T01:12:54Z" level=info msg="started backup" gl_project_path=justacec/ShinyFitProfileR relative_path=@hashed/4e/07/4e07408562bedb8b60ce05c1decfe3ad16b72230967de01f640b7e4729b49fce.git storage_name=default

time="2021-09-20T01:12:55Z" level=info msg="completed backup" gl_project_path=justacec/TemperatureAnalysis relative_path=@hashed/d4/73/d4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35.git storage_name=default

time="2021-09-20T01:12:55Z" level=info msg="started backup" gl_project_path=justacec/ShinyFitProfileR.wiki relative_path=@hashed/4e/07/4e07408562bedb8b60ce05c1decfe3ad16b72230967de01f640b7e4729b49fce.wiki.git storage_name=default

time="2021-09-20T01:12:55Z" level=warning msg="skipped backup" error="repository skipped" gl_project_path=justacec/ShinyFitProfileR.wiki relative_path=@hashed/4e/07/4e07408562bedb8b60ce05c1decfe3ad16b72230967de01f640b7e4729b49fce.wiki.git storage_name=default

All of that being said, the backup did take a while and the backup file is the same size as all of the others, approximately.

I installed though the official tagged docker images and have the following versions:
Gitlab: 14.2.4
GitLab Shell: 13.19.1
GitLab Workhorse: 14.2.4
GetLab API: 4
Ruby: 2.7.2p137
Rails: 6.1.3.2
PostgresSQL: 12.7
Redis: 6.0.14

6

I am having the same issue. I just upgraded to 14.3.2 and the issue persists. I have tried various solutions like using the rails console to recall repository sizes and invalidate caches. Nothing seems to work. Almost every repository with imported from gitea is not backing up. And a couple of new ones are doing the same.

It’s making me a bit nervous to say the least.

7

We are seeing this as well, but from a high level it appears to skip wiki and design git repositories, not the main .git repository. Perhaps skipping empty repos?

9

I don’t think that’s the same error (the previous posts mostly are about projects being skipped when taking backups), please don’t pollute threads by posting other problems to them.

In making a new thread with your issue: If those lines simply saying “.” are your work, please try to find the actual errors and include them (the output can be really long, so trying to shorten it is a good thing).

1 Like
10

I’m migrating my repositories from another platform to Gitlab. The version of gitlab installed on Ubuntu 20.04 LTS is 14.4.1 the same bug is reported. What I found strange is that the repositories are not empty, and also when restoring on another server they work.

Has anyone managed to solve this problem?

11

Guys, I believe it’s correct. Inside the repositories there is the wiki feature, apparently it is also versioned. When creating a wiki in one of the repositories where the warning was presented, the message stopped occurring. I restored a backup and everything worked as expected.

12

The relative path reads:

relative_path=@hashed/ef/2d/ef2d127de37b942baad06145e54b0c619a1f22327b2ebbcfbec78f5564afe39d.design.git

and thus ends with .design.git.

As already mentioned by outofcontrol, this is not the project repository itself, but a dedicated design repository (I couldn’t figure out what it is for. Is it related to Design management | GitLab?

Could anyone find a way how to deactivate these warnings? I think many users will have either empty .design.git or .wiki.git repositories and then these warnings should be deactivated.

13

@chraebs33light could you share how you resolved this issue? because I am have the same warnings.