I would yes. After you remove the package also make sure to delete /var/opt/gitlab and /var/log/gitlab and /etc/gitlab and also make sure /opt/gitlab doesn’t exist and delete if it does. Then install again.
I will do that and let you know about the results
In the meantime, if you can please take a look at this issue I have with Docker installation: Docker installation - Unable to change the password
I would rather use a standalone version anyway.
@iwalker After the fresh install all services is running except for I’m getting the following error:
gitlab-ctl tail
/var/log/gitlab/gitlab-workhorse/current <==
{"correlation_id":"01F5ZB9KV3HADVY0DNDKMGSJH5","duration_ms":0,"error":"badgateway: failed to receive response: dial unix /var/opt/gitlab/gitlab-rails/sockets/gitlab.socket: connect: connection refused","level":"error","method":"GET","msg":"","time":"2021-05-18T11:00:49+02:00","uri":"/-/metrics"}
{"content_type":"text/html; charset=utf-8","correlation_id":"01F5ZB9KV3HADVY0DNDKMGSJH5","duration_ms":0,"host":"127.0.0.1:6001","level":"info","method":"GET","msg":"access","proto":"HTTP/1.1","referrer":"","remote_addr":"127.0.0.1:40876","remote_ip":"127.0.0.1","route":"^/-/","status":502,"system":"http","time":"2021-05-18T11:00:49+02:00","ttfb_ms":0,"uri":"/-/metrics","user_agent":"Prometheus/2.25.0","written_bytes":2940}
How can I send you the gitlab.rb file?
Check permissions on /var/opt/gitlab/gitlab-rails directory. They should be git:root. In the gitlab-rails directory, sockets should have git:gitlab-www and the gitlab.socket file in this directory should have git:git.
If the directory permissions are OK, stop gitlab completely with:
gitlab-ctl stop
and then see if the socket still exists in gitlab-rails/sockets/ - if it does, then do this:
systemctl gitlab-runsvdir.service stop
and check if the socket exists, if it still exists, remove it from the sockets directory rm gitlab.socket.
Then do:
systemctl start gitlab-runsvdir.service
gitlab-ctl start
and check everything again. Can you tell me what changes you made to gitlab.rb file? Just the external_url, or something else?
I’ve updated the permissions so you can see it now:
ls -lh /var/opt/gitlab/ | grep gitlab-rails
drwxr-xr-x 9 git root 4.0K May 18 10:48 gitlab-rails
ls -lh | grep sockets
drwxr-x--- 2 git gitlab-www 4.0K May 18 11:58 sockets
ls -lh | grep gitlab.socket
srwxrwxrwx 1 git git 0 May 18 11:58 gitlab.socket
I also followed your instructions, removed gitlab.socket, and restarted the service you mentioned and gitlab-ctl. Still getting the same error.
I’ve made some changes to the port configurations. I think that it would be best if you can see my whole gitlab.rb file, or give me a link to the default one so I can send you the differences.
So I expect the problems are related to misconfiguration with the ports if that is the case. Ideally it would be best to leave the ports the defaults, and the only change you should make to gitlab.rb is the external_url with either http or https and also without changing the port. What is the reason for you changing the ports, rather than accepting the defaults?
The reason for not using the default port is because ports 3000 and 8080 are used by some other services on my server.
Other changes which I made on gitlab.rb file is because I needed to set in order to work on the Plesk domain.
You can see the changes on the following link: Install GitLab 11 on Ubuntu 16.04 LTS with Plesk 17 Onyx and HTTPS / SSL - Christian Kauppert
I’ve followed those instructions. Also ports 3000 and 8080 are replaced with 6001 and 6002.
Bit of an old document that, Gitlab 11, when configuring Gitlab 13. Changes for example, unicorn was replaced with puma, so in the config you should be configuring puma:
so could be a reason why you are getting unresponsive page, if gitlab is attempting to redirect to puma, and you have attempted to configure unicorn instead which isn’t completely finished in terms of enabling it.
As for the other ports, better you check the Gitlab documentation, rather than some third-party how to which is most likely out-of-date and doesn’t apply to the version you are running.
I personally recommend Gitlab on a separate server, than attempting to run it on a server that shares it’s resources with other applications and services. Far less complicated, and saves from experiencing problems like this. Not also taking into account performance issues by attempting to do too much on a single server/VM.
Thanks a lot for all the help and advice. When I got new resources (new server instance) I will try running it on a clean environment.
Also, when you have time please check the Docker installation - Unable to change the password issue I posted before.
1 Like
I don’t use docker, so won’t be able to help you with that unfortunately, I have no experience of it with gitlab.
Ok. I’ve marked your previous message as Solution, thanks for all the help once more.
1 Like