Expected response 14390 but got 1634759484
…ruby/gems/1.8/gems/mongo-1.7.1/lib/mongo/networking.rb: 165:in `receive_header'
…ruby/gems/1.8/gems/mongo-1.7.1/lib/mongo/networking.rb: 151:in `receive'
…ruby/gems/1.8/gems/mongo-1.7.1/lib/mongo/networking.rb: 118:in `receive_message'
…lib/ruby/gems/1.8/gems/mongo-1.7.1/lib/mongo/cursor.rb: 478:in `send_initial_query'
…by/gems/1.8/gems/mongo-1.7.1/lib/mongo/util/logging.rb: 32:in `instrument'
…lib/ruby/gems/1.8/gems/mongo-1.7.1/lib/mongo/cursor.rb: 473:in `send_initial_query'
…lib/ruby/gems/1.8/gems/mongo-1.7.1/lib/mongo/cursor.rb: 458:in `refresh'
…lib/ruby/gems/1.8/gems/mongo-1.7.1/lib/mongo/cursor.rb: 127:in `next_document'
…ruby/gems/1.8/gems/mongo-1.7.1/lib/mongo/collection.rb: 297:in `find_one'
…ib/ruby/gems/1.8/gems/plucky-0.3.8/lib/plucky/query.rb: 63:in `find_one'
…ib/ruby/gems/1.8/gems/plucky-0.3.8/lib/plucky/query.rb: 80:in `first'
…r-0.8.6/lib/mongo_mapper/plugins/querying/decorator.rb: 29:in `first'
…per-0.8.6/lib/mongo_mapper/plugins/dynamic_querying.rb: 17:in `send'
…per-0.8.6/lib/mongo_mapper/plugins/dynamic_querying.rb: 17:in `dynamic_find'
…per-0.8.6/lib/mongo_mapper/plugins/dynamic_querying.rb: 35:in `method_missing'
nginx + passenger
Based on the backtrace, this is a driver issue, not a mongomapper issue. I would file an issue for the driver.
This should be resolved (along with some other significant issues) in the latest version of the driver. Upgrade to 1.8.3+ and you'll see this go away.
@brandonblack @jnunemaker thanks!
Can you tell me the cause of the error it? Timeout?
And how to fix?
@brandonblack This problem is still puzzling me.
@tumayun There were actually a couple of things happening 1) external timeouts were causing socket mangling which could result in this error 2) there was an issue in the cursor when reading from secondaries where it might try to read a cursor or close an open cursor on the wrong secondary.
You can read the full release notes here:
@brandonblack Thank you very much!