Restoring Wikis fails
Summary
When restoring a gitlab backup to a standby machine, all of the wikis fail to restore, but nothing else fails.
Steps to reproduce
On main gitlab machine
gitlab-rake GZIP_RSYNCABLE=yes gitlab:backup:create
Then rsync to standby machine
On standby machine
gitlab-rake gitlab:backup:restore BACKUP=most_recent force=yes --trace
Example Project
N/A
What is the current bug behavior?
I can succesfully backup my hundreds of repos and the associated dozens of wikis, but when restoring only the repos succesfully restore. The wikis fail with the error "Error 13:CreateRepositoryFromBundle: cmd wait failed: exit status 128"
What is the expected correct behavior?
The wikis should be restored without error
Relevant logs and/or screenshots
Restore Log
* scripts/myrepo ... [DONE]
* scripts/myrepo.wiki ... [Failed] restoring scripts/myrepo.wiki wiki
Error 13:CreateRepositoryFromBundle: cmd wait failed: exit status 128
This happens for any and all wikis, but not for any of the code repos.
In the backup log, the wikis that exist show:
* scripts/myrepo ... [DONE]
[DONE] Wiki
and of course all the repos that don't have wikis show:
* scripts/johnsrepo ... [DONE]
[SKIPPED] Wiki
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
System information
System: Ubuntu 16.04
Current User: git
Using RVM: no
Ruby Version: 2.6.3p62
Gem Version: 2.7.9
Bundler Version:1.17.3
Rake Version: 12.3.3
Redis Version: 3.2.12
Git Version: 2.22.2
Sidekiq Version:5.2.7
Go Version: unknown
GitLab information
Version: 12.5.4
Revision: 63af04cacf5
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: PostgreSQL
DB Version: 10.9
URL: https://172.16.1.102
HTTP Clone URL: https://172.16.1.102/some-group/some-project.git
SSH Clone URL: git@172.16.1.102:some-group/some-project.git
Using LDAP: no
Using Omniauth: yes
Omniauth Providers: [Redacted]
GitLab Shell
Version: 10.2.0
Repository storage paths:
- default: /data/gitlab/git-data/repositories
GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell
Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 10.2.0 ? ... OK (10.2.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
3/1 ... yes
... (all yes)
375/795 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.3)
Git version >= 2.22.0 ? ... yes (2.22.2)
Git user has default SSH configuration? ... yes
Active users: ... 301
Is authorized keys file accessible? ... yes
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
Possible fixes
?