-
Notifications
You must be signed in to change notification settings - Fork 176
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
SystemExit when sidekiq restarted #97
Comments
Hi @dfguo, How are you integrating with Bugsnag? I've not seen this happen before. It might happen if you are listening for exceptions in an Conrad |
Please re-open if you can reproduce this. |
I'm getting this in Resque Scheduler too: SystemExit: exit
gems/resque-scheduler-2.5.5/lib/resque/scheduler.rb:287:in exit
from gems/resque-scheduler-2.5.5/lib/resque/scheduler.rb:287:in handle_shutdown
from gems/resque-scheduler-2.5.5/lib/resque/scheduler.rb:385:in poll_sleep
from gems/resque-scheduler-2.5.5/lib/resque/scheduler.rb:132:in block in run
from gems/resque-scheduler-2.5.5/lib/resque/scheduler.rb:123:in loop
from gems/resque-scheduler-2.5.5/lib/resque/scheduler.rb:123:in run
from gems/resque-scheduler-2.5.5/lib/resque_scheduler/cli.rb:137:in run_forever
from gems/resque-scheduler-2.5.5/lib/resque_scheduler/tasks.rb:19:in block (2 levels) in <top (required)>
from gems/rake-10.3.1/lib/rake/task.rb:240:in call
from gems/rake-10.3.1/lib/rake/task.rb:240:in block in execute
from gems/rake-10.3.1/lib/rake/task.rb:235:in each
from gems/rake-10.3.1/lib/rake/task.rb:235:in execute
from gems/rake-10.3.1/lib/rake/task.rb:179:in block in invoke_with_call_chain
from /usr/local/lib/ruby/1.9.1/monitor.rb:211:in mon_synchronize
from gems/rake-10.3.1/lib/rake/task.rb:172:in invoke_with_call_chain
from gems/rake-10.3.1/lib/rake/task.rb:165:in invoke
from gems/rake-10.3.1/lib/rake/application.rb:150:in invoke_task
from gems/rake-10.3.1/lib/rake/application.rb:106:in block (2 levels) in top_level
from gems/rake-10.3.1/lib/rake/application.rb:106:in each
from gems/rake-10.3.1/lib/rake/application.rb:106:in block in top_level
from gems/rake-10.3.1/lib/rake/application.rb:115:in run_with_threads
from gems/rake-10.3.1/lib/rake/application.rb:100:in top_level
from gems/rake-10.3.1/lib/rake/application.rb:78:in block in run
from gems/rake-10.3.1/lib/rake/application.rb:176:in standard_exception_handling
from gems/rake-10.3.1/lib/rake/application.rb:75:in run
from gems/rake-10.3.1/bin/rake:33:in <top (required)>
from bin/rake:23:in load
from bin/rake:23:in <main> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are seeing SystemExit error pretty much when we restarted our sidekiq. We didn't see it before with our previous exception vendor. What is this about? Here's the stacktrace:
SystemExitvendor/bundle/ruby/1.9.1/gems/sidekiq-2.17.0/lib/sidekiq/cli.rb:82
exit
vendor/bundle/ruby/1.9.1/gems/sidekiq-2.17.0/lib/sidekiq/cli.rb:82:in exit
from vendor/bundle/ruby/1.9.1/gems/sidekiq-2.17.0/lib/sidekiq/cli.rb:82:in rescue in run
from vendor/bundle/ruby/1.9.1/gems/sidekiq-2.17.0/lib/sidekiq/cli.rb:66:in run
from vendor/bundle/ruby/1.9.1/gems/sidekiq-2.17.0/bin/sidekiq:8:in <top (required)>
from vendor/bundle/ruby/1.9.1/bin/sidekiq:23:in load
from vendor/bundle/ruby/1.9.1/bin/sidekiq:23:in
The text was updated successfully, but these errors were encountered: