GRPC::Unavailable: 14:Connect Failed

[nanquanyuhao]

There is a bug when you backup/restore with command like this...

# backup
docker-compose run --rm gitlab app:rake gitlab:backup:create
# restore
docker-compose run --rm gitlab app:rake gitlab:backup:restore BACKUP=***

the info like this...

...
Dumping repositories ...
 * liyeheng/gs-spring-boot-docker ... [WARNING] Executing 14:Connect Failed
Ignoring error on liyeheng/gs-spring-boot-docker - Failed to backup repo
[DONE]
rake aborted!
GRPC::Unavailable: 14:Connect Failed
/home/git/gitlab/vendor/bundle/ruby/2.4.0/gems/grpc-1.11.0-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:31:in `check_status'
...

To see #1655 , @serenader2014 supply a way to handle issue but can't reslove it.

My Gitlab version is 10.6.2, and I use the version 11.3.5, it still has the problem...
Can you fix it ? Thanks...

[zer01ike]

same as your question
I use dcoker-compose to backup the gitlab
and then get a Failed to backup repo Error!

[nanquanyuhao]

same as your question
I use dcoker-compose to backup the gitlab
and then get a Failed to backup repo Error!

You can do like this...

    Starting the gitlab container
    Enter the gitlab's bash shell
    Execute /sbin/entrypoint.sh app:rake gitlab:backup:restore to restore a backup
    When restore finish, just restart gitlab container, and all is done.

[zer01ike]

Thanks !

but when i try to backup using the app:rake
i enter the gitlab container I get a error

Could not locate Gemfile or .bundle/directory

[nanquanyuhao]

Thanks !

but when i try to backup using the app:rake
i enter the gitlab container I get a error

Could not locate Gemfile or .bundle/directory

You can try the auto backup, I use it long time ...

    - GITLAB_BACKUP_SCHEDULE=daily
    - GITLAB_BACKUP_TIME=04:00

[zer01ike]

ok, I will try it !

[QuickJack]

I have tested the workaround proposed by @nanquanyuhao with 11.1.4 and can confirm that it works. Many thanks.

[stale]

This issue has been automatically marked as stale because it has not had any activity for the last 60 days. It will be closed if no further activity occurs during the next 7 days. Thank you for your contributions.