You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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. 👍
This issue seems to have popped up since we’ve upgraded to Ruby 2.1.1.
If we start our service:
And then, while it’s still starting:
If we try to stop it or restart it:
The text was updated successfully, but these errors were encountered: