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

Closed
Open
Created Feb 10, 2013 by Administrator@rootOwner

Checking Sidekiq ... note is missing RAILS_ENV=production

Created by: hotpocket

https://github.com/gitlabhq/gitlabhq/blob/stable/doc/install/installation.md

under the Check Application Status section

sudo -u gitlab -H bundle exec rake gitlab:check RAILS_ENV=production

returned Checking Sidekiq ...

Running? ... no Try fixing it: sudo -u gitlab -H bundle exec rake sidekiq:start

which should have included RAILS_ENV=production in the suggestion ... after adding that it ran correctly but the service was still not started ... after inspecting the logs I discovered I needed to do sudo -u gitlab -H mkdir -p /home/gitlab/gitlab/tmp/pids ... then ran ... sudo -u gitlab -H bundle exec rake sidekiq:start RAILS_ENV=production

which did yield the correct results starting the sidekiq service

Assignee
Assign to
Time tracking