I also run into similar problems maybe every week or so. For comparison, here's my collection of C extensions :
bcrypt-ruby-3.0.1 fast_xs-0.8.0 ffi-1.9.3 hiredis-0.4.5 kgio-2.8.0 mysql2-0.3.13 nokogiri-1.5.11 oily_png-1.1.1 posix-spawn-0.3.6 raindrops-0.12.0 rmagick-2.13.2 taglib-ruby-0.6.0 thread_safe-0.3.4 unicorn-4.6.2 websocket-driver-0.3.2 On 22 July 2014 17:39, Eric Wong <[email protected]> wrote: > Philip Cunningham <[email protected]> wrote: >> We recently experienced an issue with our staging server on Heroku. >> It's the first time we've seen this error and the staging server >> hasn't been updated in a week or so. It's not clear to me how I should >> investigate this further so I would appreciate any assistance you >> might offer. Some details are below: > >> ``` ruby version >> ruby 2.0.0p481 (2014-05-08 revision 45883) [x86_64-linux] >> ``` >> >> ``` log >> 2014-07-22T14:47:34.306596+00:00 app[web.2]: >> /app/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_request.rb:80:in >> `parse': method `hash' called on unexpected T_NODE object (0x007fa3c36823d8 >> flags=0x33b21c) (NotImplementedError) > > This is either a version mismatch from objects of different Ruby versions > or memory corruption caused by a C extension. Since your install > hasn't been touched in a week, I suspect a buggy C extension. > > Can you share a list of C extensions, in particular less popular/used > ones so others may have a look and see if there's any known issues? > > Just in case, can you ensure you're not carrying around any .so files > between different Ruby versions/installations? > > Thanks. >
