gitlab-shell.log is empty, new one provides no useful information

Summary

gitlab-shell.log is empty at original location, and new version doesn't provide sufficient information

Steps to reproduce

No idea how to reproduce this. Possibly the result of a version upgrade at some point (12.5?)

What is the current bug behavior?

The detailed logs that were once sent to /var/log/gitlab/gitlab-shell/gitlab-shell.log are now non-existent.

The "new" location at /var/log/gitlab/gitaly/gitlab-shell.log as described by https://docs.gitlab.com/ee/administration/logs.html does not provide the same or even remotely useful information. It is completely useless compared to the old logs.

What is the expected correct behavior?

We expect to see the same detailed logs in gitlab-shell.log as we did before, regardless of location.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

System information System: Current User: git Using RVM: no Ruby Version: 2.6.3p62 Gem Version: 2.7.9 Bundler Version:1.17.3 Rake Version: 12.3.3 Redis Version: 3.2.12 Git Version: 2.22.2 Sidekiq Version:5.2.7 Go Version: unknown

GitLab information Version: 12.5.4 Revision: 63af04cacf5 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 10.9 URL: https://gitlab.otxlab.net HTTP Clone URL: https://gitlab.otxlab.net/some-group/some-project.git SSH Clone URL: git@gitlab.otxlab.net:some-group/some-project.git Using LDAP: yes Using Omniauth: yes Omniauth Providers:

GitLab Shell Version: 10.2.0 Repository storage paths:

  • default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:check SANITIZE=true)

Too long to provide in text field... See attached. check.log

Edited by Rob Petti