-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Possible issue with admin web app in 2.10.1 #863
Comments
Fixed by 413b190 On Thu, Apr 18, 2013 at 1:48 PM, Marc Lennox notifications@github.comwrote:
|
Cool, what version will this get rolled into? |
2.11.0 On Thu, Apr 18, 2013 at 1:52 PM, Marc Lennox notifications@github.comwrote:
|
❤️ |
I am getting this problem regularly on version 2.11.2 when going to the worker tab: Puma 1.6.3 starting... |
Might be related to workers that exit but sidekiq looses awarenes that they have been killed. I periodically get stats on the sidekiq panel that show busy even though I know they have been killed (usually by a heroku restart). |
@robblovell You say 2.11.2 but your stack trace clearly shows differently... |
Started getting this error accessing the "Workers" page in the sidekiq admin app. Not sure if it's 2.10.1 related or not, but this is the only variable that changed. Anyone else seeing this?
The text was updated successfully, but these errors were encountered: