Infinitive Pending status for GItlab CI build
Summary
Builds are never finished - they stuck in Pending state.
Steps to reproduce
Launch the build. After the build finish - it stuck and lock further builds.
Expected behavior
Give results of the build and show Failed or Success.
Actual behavior
Pending......................................
Relevant logs and/or screenshots
pending 166197ef More verbose CI · about 13 hours ago by Rafal Zawadzki
Output of checks
Results of GitLab application Check
$ dpkg -l |grep gitlab |grep runner
ii gitlab-ci-multi-runner 1.7.1 amd64 GitLab Runner
(gitlab_1604)root@h2015:/# sudo gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...
GitLab Shell version >= 3.6.6 ? ... OK (3.6.6)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
5/2 ... ok
7/3 ... ok
4/4 ... repository is empty
2/5 ... ok
2/6 ... ok
2/7 ... ok
8/8 ... ok
9/9 ... ok
2/11 ... ok
2/12 ... ok
2/13 ... ok
2/14 ... ok
2/16 ... ok
8/17 ... ok
8/20 ... repository is empty
13/21 ... ok
8/22 ... ok
8/23 ... ok
2/24 ... ok
2/25 ... repository is empty
15/26 ... ok
2/27 ... ok
2/28 ... ok
17/29 ... ok
17/30 ... ok
2/31 ... repository is empty
2/32 ... ok
2/33 ... ok
2/34 ... ok
2/35 ... ok
8/36 ... ok
20/37 ... ok
1/38 ... repository is empty
8/39 ... ok
8/41 ... ok
8/42 ... ok
8/43 ... ok
8/44 ... ok
8/45 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 2
Try fixing it:
sudo service gitlab stop
sudo pkill -u git -f sidekiq
sleep 10 && sudo pkill -9 -u git -f sidekiq
sudo service gitlab start
Please fix the error above and rerun the checks. ### Comment from me - bluszcz - i believe it happens because i run diaspora with sidekiq on same host
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP users with access to your GitLab server (only showing the first 100 results)
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... skipped (no tmp uploads folder yet)
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: ...
5/2 ... yes
7/3 ... yes
4/4 ... yes
2/5 ... yes
2/6 ... yes
2/7 ... yes
8/8 ... yes
9/9 ... yes
2/11 ... yes
2/12 ... yes
2/13 ... yes
2/14 ... yes
2/16 ... yes
8/17 ... yes
8/20 ... yes
13/21 ... yes
8/22 ... yes
8/23 ... yes
2/24 ... yes
2/25 ... yes
15/26 ... yes
2/27 ... yes
2/28 ... yes
17/29 ... yes
17/30 ... yes
2/31 ... yes
2/32 ... yes
2/33 ... yes
2/34 ... yes
2/35 ... yes
8/36 ... yes
20/37 ... yes
1/38 ... yes
8/39 ... yes
8/41 ... yes
8/42 ... yes
8/43 ... yes
8/44 ... yes
8/45 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.1)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.7.4)
Active users: 11
Checking GitLab ... FinishedEdited by 🤖 GitLab Bot 🤖