Your message dated Mon, 15 Feb 2016 18:49:42 +0000
with message-id <e1avodo-0006hi...@franck.debian.org>
and subject line Bug#814714: fixed in gitlab 8.4.3+dfsg-7
has caused the Debian Bug report #814714,
regarding gitlab: no http interface and no error in logs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
814714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.4.3+dfsg-6
Severity: grave
Justification: renders package unusable
Hi,
this problem appeared after my upgrade to 8.4.3+dfsg-6 without me
changing anything in my configuration, so I assume that this must be
gitlab's fault, thus the high severity.
The symptom is, that since after the upgrade (and after manually
creating the /var/run/gitlab directories as I described in #814713), I
only get the following message in my browser when trying to access the
website:
502
Whoops, GitLab is taking too much time to respond.
Try refreshing the page, or going back and attempting the action again.
Please contact your GitLab administrator if this problem persists.
Now I *am* the gitlab administrator and I fail to figure out how to find
the source of the problem. My logs show the following:
root@22gitlab:~# tail -n10000 /usr/share/gitlab/log/* /var/log/gitlab/*
==> /usr/share/gitlab/log/mail_room.log <==
fatal: Not a git repository (or any of the parent directories): .git
==> /usr/share/gitlab/log/production.log <==
** [Raven] Raven 0.15.3 configured not to send errors.
** [Raven] Raven 0.15.3 configured not to send errors.
** [Raven] Raven 0.15.3 configured not to send errors.
** [Raven] Raven 0.15.3 configured not to send errors.
Scoped order and limit are ignored, it's forced to be batch order and
batch size
** [Raven] Raven 0.15.3 configured not to send errors.
Scoped order and limit are ignored, it's forced to be batch order and
batch size
==> /var/log/gitlab/sidekiq.log <==
No such file or directory @ rb_sysopen -
/var/run/gitlab/pids/sidekiq.pid
/usr/lib/ruby/vendor_ruby/sidekiq/cli.rb:355:in `initialize'
/usr/lib/ruby/vendor_ruby/sidekiq/cli.rb:355:in `open'
/usr/lib/ruby/vendor_ruby/sidekiq/cli.rb:355:in `write_pid'
/usr/lib/ruby/vendor_ruby/sidekiq/cli.rb:42:in `parse'
/usr/bin/sidekiq:12:in `<main>'
Pidfile /var/run/gitlab/pids/sidekiq.pid does not exist
2016-02-14T15:21:41.835Z 293 TID-b4ak0 INFO: Booting Sidekiq 4.0.1 with
redis options {:url=>"redis://localhost:6379", :namespace=>"resque:gitlab"}
2016-02-14T15:21:41.983Z 293 TID-b4ak0 INFO: Cron Jobs - add job with
name: stuck_ci_builds_worker
fatal: Not a git repository (or any of the parent directories): .git
2016-02-14T15:21:57.436Z 293 TID-b4ak0 INFO: Running in ruby 2.2.4p230
(2015-12-16) [x86_64-linux-gnu]
2016-02-14T15:21:57.436Z 293 TID-b4ak0 INFO: See LICENSE and the
LGPL-3.0 for licensing details.
2016-02-14T15:21:57.436Z 293 TID-b4ak0 INFO: Upgrade to Sidekiq Pro for
more features and support: http://sidekiq.org
==> /var/log/gitlab/unicorn.stderr.log <==
I, [2016-02-14T16:21:07.730554 #287] INFO -- : Refreshing Gem list
fatal: Not a git repository (or any of the parent directories): .git
I, [2016-02-14T16:21:58.169242 #287] INFO -- : listening on
addr=/var/run/gitlab/pids/gitlab.socket fd=12
I, [2016-02-14T16:21:58.170435 #287] INFO -- : listening on
addr=127.0.0.1:8080 fd=15
I, [2016-02-14T16:21:58.195925 #346] INFO -- : worker=0 ready
I, [2016-02-14T16:21:58.205334 #349] INFO -- : worker=1 ready
I, [2016-02-14T16:21:58.220556 #287] INFO -- : master process ready
I, [2016-02-14T16:21:58.223929 #352] INFO -- : worker=2 ready
==> /var/log/gitlab/unicorn.stdout.log <==
Does there exist a way to increase the verbosity of the logging so that
I can see what causes the 502 problem? Here is the (shortened, because I
have lots of repositories) output of gitlab:check:
fatal: Not a git repository (or any of the parent directories): .git
Checking GitLab Shell ...
GitLab Shell version >= 2.6.10 ? ... OK (2.6.10)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by gitlab:gitlab? ... yes
Repo base access is drwxrws---? ... yes
hooks directories in repos are links: ...
[...]
Running /usr/share/gitlab-shell/bin/check
Check GitLab API access: FAILED. code: 502
gitlab-shell self-check failed
Try fixing it:
Make sure GitLab is running;
Check the gitlab-shell configuration file:
sudo -u gitlab -H editor /usr/share/gitlab-shell/config.yml
Please fix the error above and rerun the checks.
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes
Database config exists? ... yes
Database is SQLite ... no
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? ... yes
Init script up-to-date? ... yes
projects have namespace: ...
[...]
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.2.4)
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (2.1.4)
Active users: 16
Checking GitLab ... Finished
So this is all green except for the gitlab-shell/bin/check output. But I
guess it's expected that this is red because I cannot access the web
interface through my browser either, right?
I'd appreciate some advise in how to tell you more about the reasons for
this problem.
Thanks!
cheers, josch
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 8.4.3+dfsg-7
We believe that the bug you reported is fixed in the latest version of
gitlab, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 814...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen <prav...@debian.org> (supplier of updated gitlab package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 16 Feb 2016 00:08:18 +0530
Source: gitlab
Binary: gitlab
Architecture: source all
Version: 8.4.3+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Pirate Praveen <prav...@debian.org>
Description:
gitlab - git powered software platform to collaborate on code
Closes: 814695 814713 814714
Changes:
gitlab (8.4.3+dfsg-7) unstable; urgency=medium
.
* bc should be in build-dep (Closes: #814695)
* fix pid file mismatch between /etc/default/gitlab and systemd service files
(Closes: #814714)
* use tmpfiles.d for /run/gitlab (Closes: #814713) Thanks to Christian Seiler
Checksums-Sha1:
24317248eadecb17cf19d05dcfefc397634e2837 2066 gitlab_8.4.3+dfsg-7.dsc
8922bdb0b01e45a7c9b311029889e7a1f75f6c73 32592
gitlab_8.4.3+dfsg-7.debian.tar.xz
104a2b699cb831411b02013cd3b061635378706b 11517398 gitlab_8.4.3+dfsg-7_all.deb
Checksums-Sha256:
b425398ba7b79002576ffa3106ae25794a4ce465e892b4da317c54d5e9fe06bb 2066
gitlab_8.4.3+dfsg-7.dsc
ca383259bdaaf7430eb64bfe55541431b5ff12bdfbbe67bdf2eb9cc3901664ce 32592
gitlab_8.4.3+dfsg-7.debian.tar.xz
35122341ba41b20b3aef0ac32f2494dcff4351fe22d7890242d94fca9fd55e6b 11517398
gitlab_8.4.3+dfsg-7_all.deb
Files:
748438e7f884c2a3376554389cc6bf53 2066 ruby optional gitlab_8.4.3+dfsg-7.dsc
c70f94dfd9da19ff5b49585240cb3dd3 32592 ruby optional
gitlab_8.4.3+dfsg-7.debian.tar.xz
5eae4663073dcdc1046b12a184893ccd 11517398 ruby optional
gitlab_8.4.3+dfsg-7_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWwhvdAAoJEM4fnGdFEsIqHhsP/iRWPlplTbOq7akQrD9UuxF9
qfilFY7IIKlOFxz6ktXIeWDUr9jYMoRdLPKqesNAB0GSSrQe/MnRTJ3acN6Fmptq
tkmAXqPz1yoQ6bgJ1o9PW8VRu3GadwW8/i1Rsj7vYbLDQFQfsYS47ivB8QLsC+FO
kI5gIoRi5M/VOSYnogHR0xS+vAwYvRS6SfpmqYSAhMbHzxNt61jfQY3xmoQ7O9CJ
Pm1TxHz4T3YggkDkF2wr0l3xmf+fb2OD3X6EVIpphkTgWtRId9oZJXEg3r9mRyPz
xnLegbnoW1rnbq6Puo7qD91+iV937wn3jz7xqVxDIq/ioLrQ7E/UEOPk2MOvHRp8
gSXlbr8Eg2XT4WA29sJykxfsdFYKmnyKQDOqZWOE3F1fvOCCU8BbS5+wz+sj8kf5
wBlK1o6fvoOu1Zd5lYy5COXtMX1PnyVT2FPFHf1m6xZsepcZrrzbDVHmIsACTdbQ
GWh6uqUXkCsOBnq02cda0AWcbLhaEVdIqX16JlVhgVclMb194mlXZgitaBHX4yz9
AdyHlVxFQ/rpLcRT5JpvlaNcEqsnvAqL4z9vAXV+JFIYfPUzen9RU38rr3UFvZQb
A60TsOWhvyeNMF21yiPUvC535GfCBc8gkXFF1GclN/H0G/DKM2/qhByXJhJZyqkl
GorJu+to7QEeURZyZO51
=wvaY
-----END PGP SIGNATURE-----
--- End Message ---
