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

Closed
Open
Created Nov 12, 2013 by Administrator@rootOwner

gitlab init script fails under CentOS - sudo environment problem

Created by: kosch

I've installed 6.2.3 unter CentOS 6.4. The "service gitlab start" fails with: script/web: line 21: bundle: command not found

"bundle" is located in /usr/local/bin. Unfortunality is this path part not included in PATH when using sudo. Using e.g. su - git -c ... for each command inside the init script would solve this issues and applies an appropriate user environment for execution. Furthermore "ansible" has problems with the usage of sudo inside the init script, but thats a different story.

The workaround is manually add the path to bundle inside .bash_profile.

Assignee
Assign to
Time tracking