Hi guys, I’ve been trying to get the latest version of GitLab 8.5 to work on my Ubuntu 15.10 server. I’m using from source gitlab (If I should/could use the package, I do not mind this).
I do not care about the loss of data to the gitlab instance as it was setup 6 hours prior to me upgrading.
Here are a few log files that may help you guys:
# tail /var/log/nginx/gitlab_error.log
2016/02/23 20:39:30 [crit] 5335#0: *2 connect() to unix:/home/git/gitlab/tmp/sockets/gitlab-workhorse.socket failed (13: Permission denied) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: gitlab.mydomain.com, request: "GET / HTTP/1.1", upstream: "http://unix:/home/git/gitlab/tmp/sockets/gitlab-workhorse.socket:/", host: "gitlab.mydomain.com"
# cat log/production.log
** [Raven] Raven 0.15.4 configured not to send errors. ** [Raven] Raven 0.15.4 configured not to send errors. [ActiveJob] Enqueued ActionMailer::DeliveryJob (Job ID: d8e904e2-ae31-4010-af48-719e780704f4) to Sidekiq(mailers) with arguments: "DeviseMailer", "confirmation_instructions", "deliver_now", gid://gitlab/User/1, "CsxktvQwRM4SNs3WJAkg", {} ** [Raven] Raven 0.15.4 configured not to send errors. ** [Raven] Raven 0.15.4 configured not to send errors. ** [Raven] Raven 0.15.4 configured not to send errors. ** [Raven] Raven 0.15.4 configured not to send errors. ** [Raven] Raven 0.15.4 configured not to send errors. ** [Raven] Raven 0.15.4 configured not to send errors. ** [Raven] Raven 0.15.4 configured not to send errors. ** [Raven] Raven 0.15.4 configured not to send errors.
# sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
System information
System: Ubuntu 15.10
Current User: git
Using RVM: no
Ruby Version: 2.1.7p400
Gem Version: 2.2.5
Bundler Version:1.11.2
Rake Version: 10.5.0
Sidekiq Version:4.0.1
GitLab information
Version: 8.5.0
Revision: dd94a4f
Directory: /home/git/gitlab
DB Adapter: postgresql
URL: http://gitlab.mydomain.com
HTTP Clone URL: http://gitlab.mydomain.com/some-group/some-project.git
SSH Clone URL: git@gitlab.mydomain.com:some-group/some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 2.6.10
Repositories: /home/git/repositories/
Hooks: /home/git/gitlab-shell/hooks/
Git: /usr/local/bin/git
# sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
Checking GitLab Shell ...
GitLab Shell version >= 2.6.10 ? ... OK (2.6.10) Repo base directory exists? ... yes Repo base directory is a symlink? ... no Repo base owned by git:git? ... yes Repo base access is drwxrws---? ... yes hooks directories in repos are links: ... can't check, you have no projects Running /home/git/gitlab-shell/bin/check Check GitLab API access: FAILED. code: 502 gitlab-shell self-check failed Try fixing it: Make sure GitLab is running; Check the gitlab-shell configuration file: sudo -u git -H editor /home/git/gitlab-shell/config.yml Please fix the error above and rerun the checks.
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 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? ... no Try fixing it: sudo find /home/git/gitlab/public/uploads -type d -not -path /home/git/gitlab/public/uploads -exec chmod 0700 {} \; For more information see: doc/install/installation.md in section "GitLab" Please fix the error above and rerun the checks. Init script exists? ... yes Init script up-to-date? ... yes projects have namespace: ... can't check, you have no projects Redis version >= 2.8.0? ... yes Ruby version >= 2.1.0 ? ... yes (2.1.7) Your git bin path is "/usr/local/bin/git" Git version >= 1.7.10 ? ... yes (2.4.3) Active users: 1
Checking GitLab ... Finished
# cat /home/git/gitlab-shell/config.yml
--- user: git gitlab_url: http://gitlab.mydomain.com/ http_settings: self_signed_cert: false repos_path: "/home/git/repositories/" auth_file: "/var/opt/gitlab/.ssh/authorized_keys" redis: bin: "/usr/bin/redis-cli" namespace: resque:gitlab socket: "/var/run/redis/redis.sock" log_level: INFO audit_usernames: false
Please note, “mydomain” was replaced as I do not want to expose my GitLab URL, It is set to a FQDN!
I’ve reinstalled several times… didn’t work.
GitLab starts as seen here:
/etc/init.d/gitlab restart
Shutting down GitLab Unicorn Shutting down GitLab Sidekiq Shutting down gitlab-workhorse . GitLab is not running. Starting GitLab Unicorn Starting GitLab Sidekiq Starting gitlab-workhorse
The GitLab Unicorn web server with pid 9385 is running. The GitLab Sidekiq job dispatcher with pid 9436 is running. The gitlab-workhorse with pid 9418 is running. GitLab and all its components are up and running.
But I get this when trying to access it on my browser.
Any help would be appreciated, let me know if you need any more log files or anything of that nature 
Thanks in advance dudes!
Cal