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

Closed
Open
Created Jan 10, 2014 by Administrator@rootOwner

Server Reboot Hangs at "Shutting down both Unicorn and Sidekiq..."

Created by: jawinn

When running a "sudo reboot", the server hangs with an increasing number of dots after

Shutting down both Unicorn and Sidekiq........

I'm running "GitLab 6.4.3" on Ubuntu 12.04.3 LTS. When the server reboots, I get this in some of the startup messages, which may or may not be helpful:

Starting redis-server: redis-server.                                                                  
Removing stale Sidekiq web server pid. This is most likely caused by the Sidekiq crashing the last time it ran.                                                                                             
Starting both the GitLab Unicorn and Sidekiqscript/web: line 21: bundle: command not found............. 

Also Gitlab is not running after reboot, and I have to run "sudo service gitlab start" (not sure if this is default or part of the error).

Assignee
Assign to
Time tracking