Hi,
I have GitLab CE:
System information
System: CentOS 6.6
Current User: git
Using RVM: no
Ruby Version: 2.3.6p384
Gem Version: 2.6.13
Bundler Version:1.13.7
Rake Version: 12.3.0
Redis Version: 3.2.11
Git Version: 2.14.3
Sidekiq Version:5.0.5
Go Version: unknownGitLab information
Version: 10.5.2
Revision: b951e0d
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: http://10.0.4.169:8888
HTTP Clone URL: http://10.0.4.169:8888/some-group/some-project.git
SSH Clone URL: ssh://git@10.0.4.169:8822/some-group/some-project.git
Using LDAP: yes
Using Omniauth: no
After starting: gitlab-ctl start
I have the following problem, Gitaly does not start…
In the logs I see the following error:
2018-03-14_14:35:08.43180 time=“2018-03-14T14:35:08Z” level=info msg=“Starting Gitaly” version=“Gitaly, version 0.81.0, built 20180225.183225”
2018-03-14_14:35:08.43185 time=“2018-03-14T14:35:08Z” level=warning msg=“git path not configured. Using default path resolution” resolvedPath=/opt/gitlab/embedded/bin/git
2018-03-14_14:35:08.43490 time=“2018-03-14T14:35:08Z” level=warning msg=“git path not configured. Using default path resolution” resolvedPath=/opt/gitlab/embedded/bin/git
2018-03-14_14:35:08.43505 time=“2018-03-14T14:35:08Z” level=fatal msg=“load config” config_path=/var/opt/gitlab/gitaly/config.toml error="load linguist colors: open /tmp/gitaly-linguist-path138485659: permission denied"
Does anyone know how to solve this problem?
Gitaly every second trying to start …
in the directory /tmp/ there is no file specified.
Is this a problem with permissions to the /tmp/ directory?
drwxrwxr-x+ 8 root root 4096 Mar 14 15:49 tmp
I run gitlab from the root account.
I installed GitLab 10.5.4 analogously on Ubuntu 16.04. Here, no problem, it works correctly.
What could be a problem when installing on CentOS 6.6?
The script for running gitaly is a binary file, where can I view its contents?
/opt/gitlab/embedded/bin/gitaly
I did not find the file on the disk: gitaly-linguist-path* , gitaly-linguist*, etc.
Both on Ubuntu (where it’s ok) or on CentOS (where’s the error).