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
  • #6102

Closed
Open
Created Jan 20, 2014 by Administrator@rootOwner

gitlab.socket does not exist

Created by: qguv

gitlab.socket (tmp/sockets/gitlab.socket) is not being created when gitlab is started. This causes a 502 Bad Gateway error when visiting the gitlab instance over http. I've checked and double-checked the configuration files. An entry in the nginx log looks like this:

2014/01/20 18:11:59 [crit] 1173#0: *93 connect() to
unix:/usr/share/webapps/gitlab/gitlab/tmp/sockets/gitlab.socket failed
(2: No such file or directory) while connecting to upstream, client: removed,
server: removed, request: "GET / HTTP/1.1", upstream:
"http://unix:/usr/share/webapps/gitlab/gitlab/tmp/sockets/gitlab.socket:/",
host: "removed:8080"
Assignee
Assign to
Time tracking