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

Closed
Open
Created Jun 14, 2013 by Administrator@rootOwner

[5.2.1] init.d script error

Created by: wojdec

Details When starting GitLab (5-2-stable @ 26ed59f1) with ini.d script an error appear.

Command

#>  service gitlab start

Output

rm: cannot remove `/home/git/gitlab/tmp/sockets/gitlab.socket': No such file or directory
Puma 2.0.1 starting...
* Min threads: 0, max threads: 16
* Environment: production
* Listening on tcp://127.0.0.1:9292
GitLab service started

Cause No check whether gitlab.socket exists. It doesn't exists when Puma uses tcp binding.

Solution Add a check to init.d script similar to this one below.

SOCKET_FILE=$SOCKET_PATH/gitlab.socket
! [ -e $SOCKET_FILE ] || execute "rm $SOCKET_FILE"
Assignee
Assign to
Time tracking