Workhorse still listening on socket, not tcp?


#1

//Edit: Okay, forget everything. I forgot to uncomment the lines…

Hey everyone,
I am trying to setup an instance of GitLab on Debian 8.8 with the aim of running it with an Apache proxy since there are other websites and services running on the server. That’s why I followed these instructions.

However after following all the steps I have the following problems:

  • nginx always has a timeout when executing gitlab-ctl restart although being disabled
  • gitlab-workhorse is not listening on 8181, but seems to still use the Unix socket
    -> the whole proxy configuration doesn’t work.

I’ve run gitlab-ctl reconfigure endless times, but it seems like the config files are not correctly generated. The process is started with the following arguments:

/opt/gitlab/embedded/bin/gitlab-workhorse -listenNetwork unix -listenUmask 0 -listenAddr /var/opt/gitlab/gitlab-workhorse/socket -authBackend http://localhost:8080 -authSocket /var/opt/gitlab/gitlab-rails/sockets/gitlab.socket -documentRoot /opt/gitlab/embedded/service/gitlab-rails/public -pprofListenAddr  -secretPath /opt/gitlab/embedded/service/gitlab-rails/.gitlab_workhorse_secret -config config.toml

Any idea how to fix this?