After a period of inactivity gitlab becomes unresponsive to the point of locking the server completely

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

I have a self-hosted Gitlab-CE omnibus install on my server. While it works fine for several days at a time, after a few days (best estimate is around 10-15 days) of inactivity, the server becomes completely unresponsive to the point that I can't even ssh to it...

The only way to fix the issue so far has been restarting the server

Steps to reproduce

Install a omnibus Gitlab CE on a proxmox vm with the following configuration : 4 CPUS (2 sockets, 2 cores) 16 GB of RAM available 64GB hard disk drive

FYI, the issue has been happening over several versions.

What is the current bug behavior?

Server becomes unresponsive, can't even ssh to it to restart gitlab

What is the expected correct behavior?

server should remain available at all times

Results of GitLab environment info

Expand for output related to GitLab environment info

System information
System:		Debian 8.10
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:	unknown
GitLab information
Version:	10.6.4
Revision:	dee2c87
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		https://gitlab.itspire.fr
HTTP Clone URL:	https://gitlab.itspire.fr/some-group/some-project.git
SSH Clone URL:	git@gitlab.itspire.fr:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no
GitLab Shell
Version:	6.0.4
Repository storage paths:

• default: /opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check

Checking GitLab Shell ...
GitLab Shell version >= 6.0.4 ? ... OK (6.0.4)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
4/1 ... ok
4/2 ... ok
4/3 ... ok
4/4 ... ok
4/5 ... ok
4/8 ... ok
4/9 ... ok
4/10 ... ok
4/15 ... ok
4/16 ... ok
5/19 ... ok
5/20 ... ok
4/21 ... ok
5/22 ... ok
5/23 ... ok
5/24 ... ok
5/25 ... ok
5/26 ... ok
5/27 ... ok
5/28 ... ok
4/31 ... ok
5/32 ... ok
6/34 ... ok
6/36 ... ok
5/37 ... ok
5/38 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
4/1 ... yes
4/2 ... yes
4/3 ... yes
4/4 ... yes
4/5 ... yes
4/8 ... yes
4/9 ... yes
4/10 ... yes
4/15 ... yes
4/16 ... yes
5/19 ... yes
5/20 ... yes
4/21 ... yes
5/22 ... yes
5/23 ... yes
5/24 ... yes
5/25 ... yes
5/26 ... yes
5/27 ... yes
5/28 ... yes
4/31 ... yes
5/32 ... yes
6/34 ... yes
6/36 ... yes
5/37 ... yes
5/38 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.6)
Git version >= 2.9.5 ? ... yes (2.14.3)
Git user has default SSH configuration? ... yes
Active users: ... 2
Checking GitLab ... Finished