Chart does raise a HTTP error 500 for only one repo

Hey all,

I have a local GitLab CE install using the docker image. I noticed that for only one repository of four will not display the charts page but raise a 500 error, all other repos work fine here. On twitter I was pointed to this page: and the forum here.

See the screenshots here:

Result of gitlab-rake gitlab:env:info (running as sudo docker exec -it gitlab gitlab-rake gitlab:env:info):

System information
Current User:	git
Using RVM:	no
Ruby Version:	2.3.3p222
Gem Version:	2.6.6
Bundler Version:1.13.7
Rake Version:	12.0.0
Redis Version:	3.2.5
Git Version:	2.13.5
Sidekiq Version:5.0.4
Go Version:	unknown

GitLab information
Version:	9.5.4
Revision:	fbffc27
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		http://gitlab.localhost
HTTP Clone URL:	http://gitlab.localhost/some-group/some-project.git
SSH Clone URL:	git@gitlab.localhost:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no

GitLab Shell
Version:	5.8.0
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
Hooks:		/opt/gitlab/embedded/service/gitlab-shell/hooks
Git:		/opt/gitlab/embedded/bin/git

and gitlab-rake gitlab:check:

Checking GitLab Shell ...

GitLab Shell version >= 5.8.0 ? ... OK (5.8.0)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ... 
group / problematic ... ok
group / fine1 ... ok
group / fine2 ... ok
group / fine3 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Reply by email ...

Reply by email is disabled in config/gitlab.yml

Checking Reply by email ... Finished

Checking LDAP ...

LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab ...

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? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ... 
group / problematic ... yes
group / fine1 ... yes
group / fine2 ... yes
group / fine3 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.3 ? ... yes (2.3.3)
Git version >= 2.7.3 ? ... yes (2.13.5)
Active users: ... 2

Checking GitLab ... Finished

I’ve also checked several logs but can’t find anything. Except the error 500 log line in the nginx access log, but that’s obviously not useful at all.

I’ve created one new user beside the Administrator.
It fails instantly and is not running in a timeout AFAIS (using a localhost connection)

The repositories are all cloned from an external, online git server of mine. Gitlab should act as mirror (using cronjobs on the docker host) and for things like issues and this statistic where it fails.

What else can I do to resolve this issue? Thanks in advance!

When there’s a 500 error from the web page, there should be a log entry in the production.log especially since it’s only for a particular project.
Seems like that project didn’t mirror correctly. Since it’s just a mirror, did you try re-creating that project?

1 Like

Wow, thank you! Deleting the whole project and reimporting it did the job. All fine now :slight_smile: