Your message dated Tue, 16 Feb 2016 09:54:49 +0000 with message-id <[email protected]> and subject line Bug#814714: fixed in gitlab 8.4.3+dfsg-8 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 [email protected] immediately.) -- 814714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814714 Debian Bug Tracking System Contact [email protected] 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-8 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 [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen <[email protected]> (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 [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 16 Feb 2016 13:58:16 +0530 Source: gitlab Binary: gitlab Architecture: source all Version: 8.4.3+dfsg-8 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers <[email protected]> Changed-By: Pirate Praveen <[email protected]> Description: gitlab - git powered software platform to collaborate on code Closes: 814714 Changes: gitlab (8.4.3+dfsg-8) unstable; urgency=medium . * Install tmpfiles.d/gitlab.conf and allow www-data user to read /run/gitlab (Closes: #814714) * Switch to sendmail method by default. Checksums-Sha1: 9c7be603d443ac6c7eb87dac6dcd3010c4897abe 2066 gitlab_8.4.3+dfsg-8.dsc 11bdfd5eca5878b86f5cd1ee5bbda1e1641a5e3f 32680 gitlab_8.4.3+dfsg-8.debian.tar.xz 983e92a80563bcc83de09dd9f09502d5a381f090 11517706 gitlab_8.4.3+dfsg-8_all.deb Checksums-Sha256: d10bb952cb9bdace97f1500d60ee4582022418ae6d635837da071dca47892b9e 2066 gitlab_8.4.3+dfsg-8.dsc a5a41a17a2d4d3232b7debb8d250c7e49be83dc0e6d89ea57241d9c4029701f6 32680 gitlab_8.4.3+dfsg-8.debian.tar.xz e970a07b0213267c5bb7632307feaff9892ddb786b5cb8dc1ac40e3edc45a51c 11517706 gitlab_8.4.3+dfsg-8_all.deb Files: 5f180064e991791d6e4b38a02f0faf34 2066 ruby optional gitlab_8.4.3+dfsg-8.dsc 0792f660e25fb15db4c341ca37425403 32680 ruby optional gitlab_8.4.3+dfsg-8.debian.tar.xz d5bd8b343f565b41c9636da79475935c 11517706 ruby optional gitlab_8.4.3+dfsg-8_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJWwuDqAAoJEM4fnGdFEsIqvSYP/2L0SGJ+h0yL/uWxNwLvLPhR /m/3cLQdFMZrmxdENR6uM+NU878y0ZR2hv7VUBXNSzVV4DyzlH4HK9X8kILgT3vt AW4RD9H9x0P6+4a89leW9iGqVvINtq/UFl4hKGocYT78+jyPO/o8/cXuFcI6gl3f CpTyHGsJxNdI4o4LBHFtLpxk8atemWMyEIKbs3t1eQWFQYK5q6Ts8Hvhp3sUWT+i q9bxceu9GOlwtLzmW4ZGjKNjMYolBRUOsol8nEyku9aDojIDDvdRq5R4QI28rurU +pb7WMWH8xGSbw6GCxNJynjXro+tKL3irM0B4ahAlT+LMCVmGzj/7suo48OS7lkw uOXDwCkyb7sOH+YwFtCesTzQeBu1nhFCmNJjQsAogy5afM/YH7+Rt0fkM7HlnRgt pjj2WuX5I93cuTZSUUBgyinrpMXr36bkN4tWxSy6QQQbDVtlWKdc8rmRIOm6nSvh FlZdFKC22+ZPTCQh0zEJ4bviEJnfSb6luTTIkhieNDESEs4TgMHKFgIB1ginOQGc dlsafUPwlMJ/Z+Pa7xm7cVA1fYZC0nfV/1jupSwvqYho7Qc7lXdotM8AihIPY3z8 1tAPUx7WF7O5E33Du1lPtjd5KRqfA4ZZfQZrvtrHkPIvB0HldAdUk67XrdAXiKEP 5j6Pw04GzlSwlL6ZRQBN =CbyA -----END PGP SIGNATURE-----
--- End Message ---
