CODEWITHSUNDEEP
backupgitlabgitlab-omnibusgitlab-ce
Saurabh Agrawal
Saurabh Agrawal

Reputation: 421

Gitlab CE 8.11.7 Gitlab-rake issue

I'm working with gitlab ce 8.11.7 from past one month in starting days it worked fine.
But now as I have scheduled cron job for taking complete backup of gitlab server everyday. After running gitlab-rake command to take backup my gitlab server is throwing 502 error.
Though all services are up but still it is throwing 502 error.

Please suggest me some solution or suggest any method to take incremental backup of gitlab server.

Upvotes: 2

Views: 753

Answers (1)

VonC
VonC

Reputation: 1326366

The "gitlab rake" command you might be refering to would be the ones detailed in "gitlab-ce/doc/raketasks/backup_restore.md "

Use this command if you've installed GitLab with the Omnibus package:

sudo gitlab-rake gitlab:backup:create

Use this if you've installed GitLab from source:

sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production

As mentioned in this issue, you need to check the logs to know more (like /var/log/gitlab/nginx/gitlab_error.log)

Check if sudo gitlab-ctl reconfigure and sudo gitlab-ctl restart help in your case.
As mentioned in "starting-and-stopping":

Note that on a single-core server it may take up to a minute to restart Unicorn and Sidekiq.
Your GitLab instance will give a 502 error until Unicorn is up again.

But upgrading to the latest version (8.14.x) remains one way to get past this error as well.

Upvotes: 1

Related Questions