Skip to content

Update to v8.16.3 broke the web interface in Scientific Linux 7.3

Summary

After updating the package to gitlab-ce.x86_64 8.16.3-ce.1.el7 using the RPM repo, the web interface is broken. It was working fine before the update.

I have the same problems that I had in #25159 (closed)

System: Scientific Linux 7.3

Web Server: Apache 2.4 - Using Apache forwarding

Using relative URL: https://<SERVER>/gitlab

Steps to reproduce

Update Gitlab to 8.16.3.

Expected behavior

Usable web interface.

Actual behavior

Web interface is broken.

Relevant logs and/or screenshots

I found nothing interesting in the web server logs.

Two screenshots: Captura_de_pantalla_de_2016-11-30_12-26-36 Captura_de_pantalla_de_2016-11-30_12-26-17

Output of checks

Results of GitLab application Check

Checking GitLab Shell ...

GitLab Shell version >= 4.1.1 ? ... OK (4.1.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ... 
1/8 ... ok
2/10 ... ok
2/12 ... ok
1/13 ... ok
1/14 ... ok
1/15 ... repository is empty
6/16 ... ok
1/17 ... ok
6/18 ... ok
1/19 ... 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 ...

Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
	<HIDDEN>

Checking LDAP ... Finished

Checking GitLab ...

Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... yes
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: ... 
1/8 ... yes
2/10 ... yes
2/12 ... yes
1/13 ... yes
1/14 ... yes
1/15 ... yes
6/16 ... yes
1/17 ... yes
6/18 ... yes
1/19 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.3)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.10.2)
Active users: 8

Checking GitLab ... Finished

Results of GitLab environment info

System information
System:		
Current User:	git
Using RVM:	no
Ruby Version:	2.3.3p222
Gem Version:	2.6.6
Bundler Version:1.13.7
Rake Version:	10.5.0
Sidekiq Version:4.2.7

GitLab information
Version:	8.16.3
Revision:	d225908
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		https://<MY_SERVER>/gitlab
HTTP Clone URL:	https://<MY_SERVER>/gitlab/some-group/some-project.git
SSH Clone URL:	git@<MY_SERVER>:some-group/some-project.git
Using LDAP:	yes
Using Omniauth:	no

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

Possible fixes

Unknown