Control: found -1 8.4.3+dfsg-7 Hi,
On Mon, 15 Feb 2016 18:49:42 +0000 Pirate Praveen <prav...@debian.org> wrote:
> 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.
I just installed version 8.4.3+dfsg-7 and cannot confirm that this bug is
fixed. Even after rebooting, the following situation presents itself to me:
root@22gitlab:~# systemctl status gitlab.target
● gitlab.target - GitLab Service
Loaded: loaded (/lib/systemd/system/gitlab.target; enabled)
Active: inactive (dead)
Feb 15 21:35:08 22gitlab systemd[1]: Dependency failed for GitLab
Service.
root@22gitlab:~# journalctl -xn
-- Logs begin at Mon 2016-02-15 21:35:03 CET, end at Mon 2016-02-15
21:35:10 CET. --
Feb 15 21:35:10 22gitlab systemd[1]: Unit gitlab-unicorn.service
entered failed state.
Feb 15 21:35:10 22gitlab systemd[1]: PID file /run/gitlab/sidekiq.pid
not readable (yet?) after start.
Feb 15 21:35:10 22gitlab systemd[1]: gitlab-sidekiq.service never wrote
its PID file. Failing.
Feb 15 21:35:10 22gitlab systemd[1]: Failed to start GitLab Sidekiq
Worker.
[...]
root@22gitlab:~# systemctl status gitlab-unicorn.service -l
● gitlab-unicorn.service - GitLab Unicorn Server
Loaded: loaded (/lib/systemd/system/gitlab-unicorn.service; enabled)
Active: failed (Result: exit-code) since Mon 2016-02-15 21:35:10
CET; 24s ago
Process: 177 ExecStop=/bin/sh bin/web stop (code=exited,
status=1/FAILURE)
Process: 129 ExecStart=/bin/sh bin/web start (code=exited,
status=1/FAILURE)
Main PID: 129 (code=exited, status=1/FAILURE)
Feb 15 21:35:10 22gitlab gitlab-unicorn[129]: from
/usr/lib/ruby/vendor_ruby/unicorn/configurator.rb:87:in `reload'
Feb 15 21:35:10 22gitlab gitlab-unicorn[129]: from
/usr/lib/ruby/vendor_ruby/unicorn/configurator.rb:68:in `initialize'
Feb 15 21:35:10 22gitlab gitlab-unicorn[129]: from
/usr/lib/ruby/vendor_ruby/unicorn/http_server.rb:100:in `new'
Feb 15 21:35:10 22gitlab gitlab-unicorn[129]: from
/usr/lib/ruby/vendor_ruby/unicorn/http_server.rb:100:in `initialize'
Feb 15 21:35:10 22gitlab gitlab-unicorn[129]: from
/usr/bin/unicorn_rails:209:in `new'
Feb 15 21:35:10 22gitlab gitlab-unicorn[129]: from
/usr/bin/unicorn_rails:209:in `<main>'
Feb 15 21:35:10 22gitlab gitlab-unicorn[129]: master failed to start,
check stderr log for details
Feb 15 21:35:10 22gitlab systemd[1]: gitlab-unicorn.service: main
process exited, code=exited, status=1/FAILURE
Feb 15 21:35:10 22gitlab gitlab-unicorn[177]: cat:
/run/gitlab/unicorn.pid: No such file or directory
Feb 15 21:35:10 22gitlab gitlab-unicorn[177]: Could not find a PID in
/run/gitlab/unicorn.pid
Feb 15 21:35:10 22gitlab systemd[1]: gitlab-unicorn.service: control
process exited, code=exited status=1
Feb 15 21:35:10 22gitlab systemd[1]: Unit gitlab-unicorn.service
entered failed state.
root@22gitlab:~# systemctl status gitlab-sidekiq.service -l
● gitlab-sidekiq.service - GitLab Sidekiq Worker
Loaded: loaded (/lib/systemd/system/gitlab-sidekiq.service; enabled)
Active: failed (Result: resources) since Mon 2016-02-15 21:35:10
CET; 44s ago
Process: 128 ExecStart=/bin/sh bin/background_jobs start
(code=exited, status=0/SUCCESS)
Feb 15 21:35:08 22gitlab systemd[1]: Starting GitLab Sidekiq Worker...
Feb 15 21:35:10 22gitlab systemd[1]: PID file /run/gitlab/sidekiq.pid
not readable (yet?) after start.
Feb 15 21:35:10 22gitlab systemd[1]: gitlab-sidekiq.service never wrote
its PID file. Failing.
Feb 15 21:35:10 22gitlab systemd[1]: Failed to start GitLab Sidekiq
Worker.
Feb 15 21:35:10 22gitlab systemd[1]: Unit gitlab-sidekiq.service
entered failed state.
Indeed, /run/gitlab doesn't exist on my system, so it doesn't get created.
But even after manually doing:
root@22gitlab:~# mkdir /run/gitlab
root@22gitlab:~# chown -R gitlab:gitlab /var/run/gitlab
root@22gitlab:~# systemctl restart gitlab.target
I'm getting this now:
root@22gitlab:~# systemctl status gitlab-unicorn.service -l
● gitlab-unicorn.service - GitLab Unicorn Server
Loaded: loaded (/lib/systemd/system/gitlab-unicorn.service; enabled)
Active: active (running) since Mon 2016-02-15 21:39:52 CET; 2min 26s
ago
Process: 177 ExecStop=/bin/sh bin/web stop (code=exited,
status=1/FAILURE)
Main PID: 267 (unicorn_rails)
CGroup: /system.slice/ssh.service/system.slice/gitlab-unicorn.service
├─267 unicorn_rails master -c
/usr/share/gitlab/config/unicorn.rb -E production -D
├─291 unicorn_rails worker[0] -c
/usr/share/gitlab/config/unicorn.rb -E production -D
├─294 unicorn_rails worker[1] -c
/usr/share/gitlab/config/unicorn.rb -E production -D
└─297 unicorn_rails worker[2] -c
/usr/share/gitlab/config/unicorn.rb -E production -D
Feb 15 21:39:52 22gitlab systemd[1]: Started GitLab Unicorn Server.
root@22gitlab:~# systemctl status gitlab-sidekiq.service -l
● gitlab-sidekiq.service - GitLab Sidekiq Worker
Loaded: loaded (/lib/systemd/system/gitlab-sidekiq.service; enabled)
Active: active (running) since Mon 2016-02-15 21:39:56 CET; 2min 41s
ago
Process: 212 ExecStart=/bin/sh bin/background_jobs start
(code=exited, status=0/SUCCESS)
Main PID: 273 (sidekiq)
CGroup: /system.slice/ssh.service/system.slice/gitlab-sidekiq.service
└─273 sidekiq 4.0.1 gitlab [0 of 25 busy]
Feb 15 21:39:56 22gitlab systemd[1]: PID file /run/gitlab/sidekiq.pid
not readable (yet?) after start.
Feb 15 21:39:56 22gitlab systemd[1]: gitlab-sidekiq.service:
Supervising process 273 which is not our child. We'll most likely not notice
when it exits.
Feb 15 21:39:56 22gitlab systemd[1]: Started GitLab Sidekiq Worker.
root@22gitlab:~# systemctl status gitlab-workhorse.service -l
● gitlab-workhorse.service - Gitlab Workhorse handles slow HTTP
requests for Gitlab.
Loaded: loaded (/lib/systemd/system/gitlab-workhorse.service;
enabled)
Active: active (running) since Mon 2016-02-15 21:39:53 CET; 2min 50s
ago
Process: 215 ExecStart=/usr/share/gitlab/bin/daemon_with_pidfile
/run/gitlab/gitlab-workhorse.pid gitlab-workhorse -listenUmask 0 -listenNetwork
unix -listenAddr /run/gitlab/gitlab-workhorse.socket -authBackend
http://127.0.0.1:8080 -authSocket /run/gitlab/gitlab.socket -documentRoot
/usr/share/gitlab/public >>/var/log/gitlab/gitlab-workhorse.log 2>&1
(code=exited, status=0/SUCCESS)
Main PID: 248 (gitlab-workhors)
CGroup:
/system.slice/ssh.service/system.slice/gitlab-workhorse.service
└─248 gitlab-workhorse -listenUmask 0 -listenNetwork unix
-listenAddr /run/gitlab/gitlab-workhorse.socket -authBackend
http://127.0.0.1:8080 -authSocket /run/gitlab/gitlab.socket -documentRoot
/usr/share/gitlab/public >>/var/log/gitlab/gitlab-workhorse.log 2>&1
As you can see, there seem to be still some problems as evident from the
"status=1/FAILURE" in unicorn and "/run/gitlab/sidekiq.pid not readable" in
sidekiq.
The good news though is, that after having manually created /run/gitlab, the
web interface works now. This at least lets me use my gitlab instance again
until the next reboot when I have to manually create /run/gitlab again...
Thanks!
cheers, josch
signature.asc
Description: signature
