Can't change project settings after backup & restore


I have a Synology NAS, with the docker version of Gitlab installed. I have Hyper Backup configured to save all folders and application data (including the docker/gitlab folder). I used backup & restore recently to switch hard drives in the NAS and I noticed that since I did this I am unable to change settings (e.g. rename, delete) on projects that have been created before the backup & restore I did.

When I hit save, Gitlab returns a 500 error with “Whoops, something went wrong on our end”. Other things work, e.g. I’m able to create commits in these repositories. Repositories I have created since then have no issues.

I have since found tutorials on how to back up Gitlab on Synology (Synology GitLab Backup and Restore), and this is not how I did it, I just backed up the folder structure for docker.

Is there a way I can salvage my installation of Gitlab? Luckily no data was lost, so I could clone all of the projects to my PC and do a clean install, I’m looking for an easier way to do this.

I found some related issues here (Page shows 500 Whoops, something went wrong on our end), however I’m having trouble issuing the suggested commands in the docker version of Gitlab. I can get into my docker container and run a gitlab:check with rake like this:

git@synology_gitlab:~/gitlab/bin$ ./rake gitlab:check --trace
(in /home/git/gitlab)
** Invoke gitlab:check (first_time)
** Invoke gitlab_environment (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute gitlab_environment
** Execute gitlab:check
Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 9.1.0 ? ... OK (9.1.0)
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK

Access to /home/git/.ssh/authorized_keys: 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? ... skipped (no tmp uploads folder yet)
Init script exists? ... yes
Init script up-to-date? ... yes
Projects have namespace: ... 
(Returned yes for all of the projects.)
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.5.7)
Git version >= 2.21.0 ? ... yes (2.23.0)
Git user has default SSH configuration? ... yes
Active users: ... 3

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished

However, I can’t find an executable for gitlab-ctl to get the logs:

git@synology_gitlab:~/gitlab/bin$ ls
background_jobs  changelog  daemon_with_pidfile  parallel-rsync-repos       profile-url  rake   rspec-stackprof  setup   update  web_puma
bundle           check      mail_room    rails        rspec  secpick          spring  web     with_env

Thank you!

Best regards,