Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #2668

Closed
Open
Created Jan 19, 2013 by Administrator@rootOwner

timeout in config/unicorn.rb.example

Created by: darinkes

Unicorn currently has a timeout of 30 seconds. In my virtual machine this lead to "502 Bad Gateway"-Errors and error logs with " 2013/01/19 18:48:12 [error] 51875#0: *3 connect() to unix:/home/gitlab/gitlab/tmp/sockets/gitlab.socket failed (111: Connection refused) while connecting to upstream, client: 192.168.2.103, server: gitlab.home.net, request: "GET /users/sign_in HTTP/1.1", upstream: "http://unix:/home/gitlab/gitlab/tmp/sockets/gitlab.socket:/users/sign_in", host: "192.168.2.104" "

Increasing the timeout to 300 fixed the issue.

Seems to be related with https://github.com/gitlabhq/gitlabhq/issues/694. But I don't understand why gitlabs nginx conf was fixed and unicorn.rb still has 30 seconds.

Assignee
Assign to
Time tracking