Mirroring from local installation to Gitlab.com fail

mirroring

#1

Hi,

I try to enable mirroring between a local gitlab server to gitlab.com.

I successfully enable few repository, but some just don’t want to work, they give me this error :

2:ArgumentError: invalid byte sequence in US-ASCII

I look for the log and find this in the /var/log/gitlab/sidekiq/current :

2019-01-09_14:22:25.30800 2019-01-09T14:22:25.307Z 23198 TID-orrel95wu RepositoryUpdateRemoteMirrorWorker JID-577a5f60341c60b1064c5a00 INFO: fail: 102.232 sec
2019-01-09_14:22:25.30824 2019-01-09T14:22:25.308Z 23198 TID-orrel95wu WARN: {“context”:“Job raised exception”,“job”:{“class”:“RepositoryUpdateRemoteMirrorWorker”,“args”:[9,“2019-01-09 15:18:20 +0100”],“retry”:3,“queue”:“repository_update_remote_mirror”,“dead”:false,“jid”:“577a5f60341c60b1064c5a00”,“created_at”:1547043500.6264055,“correlation_id”:“NL9AL4gIpk2”,“enqueued_at”:1547043643.6258698,“error_message”:“2:ArgumentError: invalid byte sequence in US-ASCII”,“error_class”:“RepositoryUpdateRemoteMirrorWorker::UpdateError”,“failed_at”:1547043599.9477122,“retry_count”:0},“jobstr”:"{“class”:“RepositoryUpdateRemoteMirrorWorker”,“args”:[9,“2019-01-09 15:18:20 +0100”],“retry”:3,“queue”:“repository_update_remote_mirror”,“dead”:false,“jid”:“577a5f60341c60b1064c5a00”,“created_at”:1547043500.6264055,“correlation_id”:“NL9AL4gIpk2”,“enqueued_at”:1547043643.6258698,“error_message”:“2:ArgumentError: invalid byte sequence in US-ASCII”,“error_class”:“RepositoryUpdateRemoteMirrorWorker::UpdateError”,“failed_at”:1547043599.9477122,“retry_count”:0}"}
2019-01-09_14:22:25.30840 2019-01-09T14:22:25.308Z 23198 TID-orrel95wu WARN: RepositoryUpdateRemoteMirrorWorker::UpdateError: 2:ArgumentError: invalid byte sequence in US-ASCII
2019-01-09_14:22:25.30851 2019-01-09T14:22:25.308Z 23198 TID-orrel95wu WARN: /opt/gitlab/embedded/service/gitlab-rails/app/workers/repository_update_remote_mirror_worker.rb:28:in `perform’

But it’s not very useful…

Any idea ?

Thanks


#2

Hi,
i’ve got the same issue. Do you have a solution ?


#3

Hi,

Still have the same issue with the very last update :

2:ArgumentError: invalid byte sequence in US-ASCII


#4

Still no solution ?

I can’t find any similar issue on google…