Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't restart unicorn #8

Open
bscott opened this issue Jun 19, 2014 · 2 comments
Open

Can't restart unicorn #8

bscott opened this issue Jun 19, 2014 · 2 comments

Comments

@bscott
Copy link

bscott commented Jun 19, 2014

When running deploy, see weird output from the unicorn task

INFO[5c90314d] Running /usr/bin/env sudo /etc/init.d/nginx reload on x.x.x.x
DEBUG[5c90314d] Command: /usr/bin/env sudo /etc/init.d/nginx reload
DEBUG[5c90314d]      * Reloading nginx configuration nginx       
DEBUG[5c90314d]     [80G
DEBUG[5c90314d]      
DEBUG[5c90314d]     
DEBUG[5c90314d]     [74G
DEBUG[5c90314d]     [ OK ]
DEBUG[5c90314d]     
INFO[5c90314d] Finished in 0.134 seconds with exit status 0 (successful).
INFO[93cdc175] Running /usr/bin/env service  restart on x.x.x.x
DEBUG[93cdc175] Command: /usr/bin/env service  restart
DEBUG[93cdc175]     restart: unrecognized service
DEBUG[93cdc175]     
cap aborted!

@bruno-
Copy link
Member

bruno- commented Jun 19, 2014

Hey, thanks for reporting.
I've never had this issue before so I'll need your help in debugging this.

  • are you deploying a rails app?
  • which capistrano-unicorn-nginx gem version are you using?
  • pasting other files (Capfile, deploy.rb, production.rb) to a service like gist or http://pastie.org/ would be useful
  • did you update the value of unicorn_service option somewhere? Example set :unicorn_service, "something"?

Unicorn restart task is really simple, it's just one line really, here.

It seems you're missing the value from the unicorn_service option. By default it should be something like: "unicorn_appname_production".
I'm guessing you overrode that somewhere?

@thejchap
Copy link

For what its worth I ran into this too and the 'no such service' wasn't what was actually wrong...it was just the last thing in the logs before something else broke (found in app/shared/log/unicorn.stderr.log)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants