Closed nilbus closed 9 years ago
The error can also manifest via foreman:
/Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/lib/foreman/engine.rb:226:in `synchronize': can't be called from trap context (ThreadError)
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/lib/foreman/engine.rb:226:in `output_with_mutex'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/lib/foreman/engine.rb:232:in `system'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/lib/foreman/engine.rb:305:in `terminate_gracefully'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/lib/foreman/engine.rb:41:in `block in start'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/lib/foreman/engine.rb:290:in `call'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/lib/foreman/engine.rb:290:in `wait2'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/lib/foreman/engine.rb:290:in `watch_for_termination'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/lib/foreman/engine.rb:48:in `start'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/lib/foreman/cli.rb:40:in `start'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/thor-0.16.0/lib/thor/task.rb:27:in `run'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/thor-0.16.0/lib/thor/invocation.rb:120:in `invoke_task'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/thor-0.16.0/lib/thor.rb:275:in `dispatch'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/thor-0.16.0/lib/thor/base.rb:425:in `start'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/gems/foreman-0.60.2/bin/foreman:7:in `<top (required)>'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/bin/foreman:23:in `load'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/bin/foreman:23:in `<main>'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/bin/ruby_noexec_wrapper:14:in `eval'
from /Users/nilbus/.rvm/gems/ruby-2.0.0-p0/bin/ruby_noexec_wrapper:14:in `<main>'
Updating the thread_safe
and atomic
gems to the latest did not resolve the issue.
Ruby 2 detects potential deadlocks that earlier versions did not. See https://bugs.ruby-lang.org/issues/7917. The daemon does not run under ruby 2 because of this error.
The traceback suggests the issue may be with the old version of rails or threadsafe that we're using.