I went to connect to my GitLab box today and received the error:
Whoops, something went wrong on our end.
I headed into the logs and couldn’t find much, but after some searching I came across
Running this I found that the Postgres socket wasn’t where GitLab thought it should be (/var/opt/gitlab/postgresql/.s.PGSQL.5432). So I headed into the Postgres conf file and changed
unix_socket_directories to point to the ‘correct’ location.
Postgres then complained that it didn’t have permission to that directory. I took a look and the perms were set to
gitlab-sql:gitlab-sql, so I changed them to
postgres:postgres and Postgres restarted, creating the file.
gitlab-rake gitlab:check I now get:
# gitlab-rake gitlab:check Checking GitLab Shell ... GitLab Shell version >= 2.6.5 ? ... OK (2.6.5) 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: ... rake aborted! PG::ConnectionBad: FATAL: Peer authentication failed for user "gitlab"
And incase it matters:
# grep git /etc/passwd git:x:999:999::/var/opt/gitlab:/bin/sh gitlab-www:x:998:998::/var/opt/gitlab/nginx:/bin/false gitlab-redis:x:997:997::/var/opt/gitlab/redis:/bin/nologin gitlab-psql:x:996:996::/var/opt/gitlab/postgresql:/bin/sh
I’m running on Ubuntu 14.04.3, 64-bit
As far as I know I’m running the latest and greatest GitLab—though I don’t recall if I installed from source or via
Looks like I’m running PostgreSQL 9.3
I have a script to install security updates and reboot the server if required, it looks like the machine was rebooted yesterday morning. I last logged into the web interface about a week ago and everything was fine then.
Since everything has gone smoothly with GitLab, I’ve not really played with it, and although I have some DB experience it is not with Postgres…
Any troubleshooting help would be great.