Push sometimes doesn't register
Created by: doenietzomoeilijk
This issue might be related to #9945 (closed), but the reporter didn't have the same error in their logs so I've decided to open a separate issue.
After upgrading to 8.3.2, we sometimes see pushes not resulting in a build, as in "it never reaches CI", it doesn't even show up in the activity log. Pushing again (after adding a newline to a readme or something silly like that) usually gets the build going. I haven't been able to reliably reproduce the behaviour, however, I did notice this in the sidekiq.log:
2016-01-05T16:01:17.323Z 12374 TID-12myns WARN: {"class"=>"PostReceive", "args"=>["/gitlab/repositories/XXX/YYY.git", "key-ZZZ", "STUFF\n"]}
2016-01-05T16:01:17.323Z 12374 TID-12myns WARN: Errno::ECONNREFUSED: Connection refused - connect(2) for nil port 80
2016-01-05T16:01:17.323Z 12374 TID-12myns WARN: /opt/gitlab/embedded/lib/ruby/2.1.0/net/http.rb:879:in `initialize'
...followed by a lengthy trace that's probably not needed here (but I could produce it if needed). This error pops up every time someone has a non-triggering push, so it seems the two are related. Not sure what it's supposed to connect to, but it seems to me connecting to nil
is never going to work... (I'm not a Ruby dev, but I'd guess nil
is equivalent to null
or None
).
Env info:
System information
System: Ubuntu 14.04
Current User: git
Using RVM: no
Ruby Version: 2.1.7p400
Gem Version: 2.5.1
Bundler Version:1.10.6
Rake Version: 10.4.2
Sidekiq Version:4.0.1
GitLab information
Version: 8.3.2
Revision: fbb8b6e
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: http://gitlab.vdlp.nl
HTTP Clone URL: http://gitlab.vdlp.nl/some-group/some-project.git
SSH Clone URL: [email protected]:some-group/some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 2.6.9
Repositories: /gitlab/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks/
Git: /opt/gitlab/embedded/bin/git
Running gitlab:check
shows green across the board.
Reconfiguring / restarting GitLab hasn't solved the issue.
Any ideas?