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

Sending ‘stop’ or ‘restart’ to ‘starting’ service gives SystemStackError #8

Open
sentience opened this issue Mar 27, 2014 · 1 comment

Comments

@sentience
Copy link

This issue seems to have popped up since we’ve upgraded to Ruby 2.1.1.

If we start our service:

$ sudo bluepill myapp start
Sent start to:
  :myapp_unicorn
  :myapp_sidekiq

And then, while it’s still starting:

$ sudo bluepill myapp status
myapp_unicorn(pid:): starting
myapp_sidekiq(pid:): starting

If we try to stop it or restart it:

$ sudo bluepill myapp stop
Received error from server:
#<SystemStackError: stack level too deep>
(eval):17

$ sudo bluepill myapp restart
Received error from server:
#<SystemStackError: stack level too deep>
(eval):17
@cpence
Copy link

cpence commented Nov 2, 2014

I was seeing the same error when I had a misconfiguration in the services themselves, so that they never leave the starting state. When you go to bring bluepill down to refresh the configuration, you get this error, and it was confusing me -- this explanation makes perfect sense. 👍

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

2 participants