Net::HTTP::Persistent::Error

[joermungandr]

Does anyone know this error? I tried a dirty fix described on this blog, which works at the moment.
http://scottwb.com/blog/2013/11/09/defeating-the-infamous-mechanize-too-many-connection-resets-bug/

/home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/protocol.rb:158:in rescue in rbuf_fill': too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 2056 requests on 8487460, last used 134.225994638 seconds ago (Net::HTTP::Persistent::Error) from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/protocol.rb:152:inrbuf_fill'
from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/protocol.rb:104:in read' from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/http/response.rb:316:inensure in read_chunked'
from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/http/response.rb:316:in read_chunked' from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/http/response.rb:276:inblock in read_body_0'
from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/http/response.rb:250:in inflater' from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/http/response.rb:274:inread_body_0'
from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/http/response.rb:201:in read_body' from /home/ss338518/.rvm/gems/ruby-2.0.0-p195/gems/mechanize-2.7.3/lib/mechanize/http/agent.rb:903:inresponse_read'
from /home/ss338518/.rvm/gems/ruby-2.0.0-p195/gems/mechanize-2.7.3/lib/mechanize/http/agent.rb:262:in block in fetch' from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/http.rb:1413:inblock (2 levels) in transport_request'
from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/http/response.rb:162:in reading_body' from /home/ss338518/.rvm/rubies/ruby-2.0.0-p195/lib/ruby/2.0.0/net/http.rb:1412:inblock in transport_request'

[developerinlondon]

it looks like a duplicate of #123 ?

theres a few options they mentioed on that thread you can try.

[leejarvis]

Yeah this is a dupe, I'm afraid I don't have a good answer for you. I'm closing this to keep the discussion in that thread