gitlabhq-10.7-gitaly.service: start condition failed
On my first try of the systemd service files:
$ systemctl start gitlabhq.target
I found that gitaly didn't start:
$ systemctl status gitlabhq-10.7-gitaly.service
● gitlabhq-10.7-gitaly.service - Gitlab Gitaly handles Gitlab RPC calls.
Loaded: loaded (/etc/systemd/system/gitlabhq-10.7-gitaly.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2018-04-26 19:00:55 CEST; 3min 1s ago
Condition: start condition failed at Thu 2018-04-26 19:00:55 CEST; 3min 1s ago
└─ ConditionPathExists=/opt/gitlabhq-10.7/tmp/sockets/gitaly.socket was not met
Process: 19320 ExecStart=/usr/bin/gitlab-gitaly ${GITALY_ARGS} (code=exited, status=1/FAILURE)
Main PID: 19320 (code=exited, status=1/FAILURE)
The comment in the service file:
# Check if gitaly is disabled in gitlab.yml (socket not created by gitlab-unicorn)
ConditionPathExists=/opt/gitlabhq-10.7/tmp/sockets/gitaly.socket
gives a hint, why this condition w=once was added. But if I recall correctly gitaly is mandatory now. And the socket is definitely not created by unicorn but by gitaly.
After removing the condition gitaly starts fine.