WebEntity / Installation-guide-for-GitLab-on-OS-X

Installation guide for GitLab on OS X
236 stars 67 forks source link

Error 502 (Whoops, GitLab is taking too much time to respond.) #60

Open znkd opened 8 years ago

znkd commented 8 years ago

Dear all, caught error 502(Whoops, GitLab is taking too much time to respond.) Please give me some advice. thanks.

env: bash-3.2$ bundle exec rake gitlab:env:info RAILS_ENV=production

System information System:
Current User: git Using RVM: no Ruby Version: 2.1.6p336 Gem Version: 2.2.3 Bundler Version:1.10.6 Rake Version: 10.4.2 Sidekiq Version:3.3.0

GitLab information Version: 8.1.4 Revision: 4d7216a Directory: /Users/git/gitlab DB Adapter: postgresql URL: http://localhost HTTP Clone URL: http://localhost/some-group/some-project.git SSH Clone URL: git@localhost:some-group/some-project.git Using LDAP: no Using Omniauth: no

GitLab Shell Version: 2.6.5 Repositories: /Users/git/repositories/ Hooks: /Users/git/gitlab-shell/hooks/ Git: /usr/local/bin/git

bash-3.2$ bundle exec rake gitlab:check RAILS_ENV=production Checking GitLab Shell ...

GitLab Shell version >= 2.6.5 ? ... OK (2.6.5) Repo base directory exists? ... yes Repo base directory is a symlink? ... no Repo base owned by git:git? ... yes Repo base access is drwxrws---? ... yes hooks directories in repos are links: ... can't check, you have no projects Running /Users/git/gitlab-shell/bin/check Check GitLab API access: FAILED: Failed to connect to internal API gitlab-shell self-check failed Try fixing it: Make sure GitLab is running; Check the gitlab-shell configuration file: sudo -u git -H editor /Users/git/gitlab-shell/config.yml Please fix the error above and rerun the checks.

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... no Try fixing it: sudo -u git -H RAILS_ENV=production bin/background_jobs start For more information see: doc/install/installation.md in section "Install Init Script" see log/sidekiq.log for possible errors Please fix the error above and rerun the checks.

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: ... can't check, you have no projects Redis version >= 2.4.0? ... yes Ruby version >= 2.1.0 ? ... yes (2.1.6) Your git bin path is "/usr/local/bin/git" Git version >= 1.7.10 ? ... yes (2.6.1) Active users: 1

Checking GitLab ... Finished

CiTroNaK commented 8 years ago

You should check logs at /Users/git/gitlab/log/.

znkd commented 8 years ago

oh,yes.

How could I make the 'socket' to resolve the error in gitlab_error.log?

gitlab_error.log:
2015/11/18 17:31:24 [crit] 1756#0: *12 connect() to unix:/Users/git/gitlab/tmp/sockets/gitlab.socket failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: 127.0.0.1, request: "GET / HTTP/1.1", upstream: "http://unix:/Users/git/gitlab/tmp/sockets/gitlab.socket:/", host: "127.0.0.1"
2015/11/18 20:24:24 [crit] 1756#0: *14 connect() to unix:/Users/git/gitlab/tmp/sockets/gitlab.socket failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: 127.0.0.1, request: "GET / HTTP/1.1", upstream: "http://unix:/Users/git/gitlab/tmp/sockets/gitlab.socket:/", host: "127.0.0.1"
2015/11/18 20:43:43 [crit] 1756#0: *16 connect() to unix:/Users/git/gitlab/tmp/sockets/gitlab.socket failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: 127.0.0.1, request: "GET / HTTP/1.1", upstream: "http://unix:/Users/git/gitlab/tmp/sockets/gitlab.socket:/", host: "127.0.0.1"

gitlab-shell.log:
W, [2015-10-15T17:55:57.462328 #7286]  WARN -- : Failed to connect to internal API <GET http://localhost:8080//api/v3/internal/check>: #<Errno::ECONNREFUSED: Connection refused - connect(2)>
W, [2015-10-15T18:02:31.351197 #7381]  WARN -- : Failed to connect to internal API <GET http://localhost:8080//api/v3/internal/check>: #<Errno::ECONNREFUSED: Connection refused - connect(2)>
E, [2015-11-18T17:17:06.861068 #1824] ERROR -- : API call <GET http://localhost//api/v3/internal/check> failed: 502 => <<!DOCTYPE html>
<html>
<head>
  <title>GitLab is not responding (502)</title>
  <link href="/static.css" media="screen" rel="stylesheet" type="text/css" />
</head>
<body>
  <h1>502</h1>
  <h3>Whoops, GitLab is taking too much time to respond.</h3>
  <hr/>
  <p>Try refreshing the page, or going back and attempting the action again.</p>
  <p>Please contact your GitLab administrator if this problem persists.</p>
</body>
</html>
>.
W, [2015-11-18T20:39:52.925814 #37306]  WARN -- : Failed to connect to internal API <GET http://localhost:8080//api/v3/internal/check>: #<Errno::ECONNREFUSED: Connection refused - connect(2) for "localhost" port 8080>
prankkelkar commented 5 years ago

Even i am facing same issue any updates?