Bill, Thanks for the thoughts. The log of responses from couch are all 200's and 300's as you would expect. Up until it stops serving any requests, but I didn't see any 500s.
When couch becomes unresponsive futon is also inaccessible. Ian On Mon, Aug 8, 2016 at 3:42 PM, Bill Stephenson <[email protected]> wrote: > I’m not a CouchDB expert but I wonder if you’re logging the responses to > your requests, and when you say it becomes unresponsive I wonder what > happens when you login to Futon? Does it not respond as well? > > Kindest Regards, > > Bill Stephenson > Tech Support > www.ezInvoice.com <http://www.ezinvoice.com/> > 1-417-546-8390 > > > On Aug 8, 2016, at 5:32 PM, Ian Danforth <[email protected]> > wrote: > > > > Hello! > > > > First post to the list so please forgive any faux-pas. I'm running > couchdb > > 1.5.0 on Ubuntu 14.04 and I am consistently running into a state where, > > after 14 days of uptime on the computer, couchdb becomes unresponsive. > > Requests to the db start queueing up until all I'm getting from the > python > > client are 599 relax exceptions. > > > > couch.couch.CouchException: HTTP 599: Unknown > > > > Asking the service to stop and restart does not recover and > > /var/log/couchdb/couch.log doesn't have any errors. > > > > I have been unable to find reports of similar errors in various Google > > searches, so I thought I'd ask here. Additional debugging and logging > > suggestions are welcome! > > > > -- > > Ian Danforth > > Fetch Robotics > > Lead Robotics Engineer > > 650-391-4467 > > -- Ian Danforth Fetch Robotics Lead Robotics Engineer 650-391-4467
