Bug#918070: gitaly: Expects gitlab socket directory

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#918070: gitaly: Expects gitlab socket directory

Dominik George-7
Package: gitaly
Version: 0.129.0+debian-3
Severity: normal

gitaly tries to create a asocket in /run/gitlab/sockets when starting up.
However, when it tries that, that directory does not exist.  Manually
creating it and then starting gitaly works.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gitaly depends on:
ii  gitlab-common               11.5.5+dfsg-1
ii  libc6                       2.28-4
ii  pipexec                     2.5.5-2
ii  procps                      2:3.3.15-2
ii  ruby                        1:2.5.1
ii  ruby-activesupport          2:4.2.10-1
ii  ruby-faraday                0.13.1-2
pn  ruby-gitaly-proto           <none>
ii  ruby-github-linguist        6.4.0-2
ii  ruby-github-markup          1.7.0+dfsg-2
ii  ruby-gollum-lib             4.2.7.5-3
ii  ruby-gollum-rugged-adapter  0.4.4.1-2
ii  ruby-google-protobuf        3.6.1.3-1
ii  ruby-grpc                   1.16.1-1
ii  ruby-licensee               8.9.2-1
ii  ruby-rugged                 0.27.4+ds-1
ii  ruby-sentry-raven           2.7.4-1

gitaly recommends no packages.

gitaly suggests no packages.

-- no debconf information

Reply | Threaded
Open this post in threaded view
|

Bug#918070: gitaly: Expects gitlab socket directory

Julian Calaby
Package: gitaly
Version: 0.129.0+debian-3
Followup-For: Bug #918070

Dear Maintainer,

Log messages when it fails:

systemd[1]: Started Gitaly.
gitaly[888]: time="2019-01-10T21:51:37+11:00" level=info msg="Starting Gitaly" version="Gitaly, version 0.129.0+debian, built "
gitaly[888]: time="2019-01-10T21:51:37+11:00" level=warning msg="git path not configured. Using default path resolution" resolvedPath=/usr/bin/git
gitaly[888]: time="2019-01-10T21:51:37+11:00" level=warning msg="git path not configured. Using default path resolution" resolvedPath=/usr/bin/git
gitaly[888]: time="2019-01-10T21:51:37+11:00" level=fatal msg="configure unix listener" error="listen unix /run/gitlab/sockets/private/gitaly.socket: bind: no such file or directory"
systemd[1]: gitaly.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: gitaly.service: Failed with result 'exit-code'.
systemd[1]: gitaly.service: Service RestartSec=100ms expired, scheduling restart.
systemd[1]: gitaly.service: Scheduled restart job, restart counter is at 4.
systemd[1]: Stopped Gitaly.

The rest of the gitlab services are running at this time.

Thanks,

Julian Calaby

Reply | Threaded
Open this post in threaded view
|

Bug#918070: confirm this bug

Dragos Jarca
In reply to this post by Dominik George-7
Confirm this bug.

Suppose that is in conjunction with systemd not initd.

Gitaly don't start. Check log...see that /run/gitlab/sockets/private
don't exists...ok...create it:

mkdir /run/gitlab/sockets/private
chown gitlab:www-data /run/gitlab/sockets/private

and systemctl start gitaly work fine.

But the problem is afret restart, shutdown, etc...the system - the dir
private disapear. Don't figure out who remove: gitaly, gitlab, other...

And seems that with systemd the following from /etc/init.d/gitaly is not
executed:

## RuntimeDirectory
mkdir -p /run/gitlab/sockets/private
chown ${DAEMON_USER}:${DAEMON_GROUP} /run/gitlab/sockets/private

Dragos