I've seen this happen a few times during deploys/restarts, and I just got a fresh backtrace, so I thought I'd bring this up.
The exception message I get is: Mongo::ConnectionFailure: Failed to connect to host xxx.yyy.zzz.com and port 12345: Interrupted system call - connect(2) Basically, it looks like unicorn is interrupting connect(2) calls when an underlying library is making a socket connection. Backtrace: https://gist.github.com/1158216 Mongo pool.rb: https://github.com/mongodb/mongo-ruby-driver/blob/1.3.1/lib/mongo/util/pool.rb I don't know if this is a unicorn thing or a Mongo implementation problem, but I'm pretty sure I've seen this happen before with Net::HTTP. I'll try to locate that error. -- alex sharp github.com/ajsharp twitter.com/ajsharp alexjsharp.com _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
