[Neo4j] Re: BadStatusLine with py2neo on CentOS6.4

2014-04-05 Thread Alan Robertson
Lots of Ubuntu clients, but in terms of servers, Red Hat (and CentOS and Scientific Linux) are more than 70% of the market. In the cloud, perhaps a little less so... On 04/05/2014 05:01 PM, Nigel Small wrote: > You must move in different server circles to me as I see far more > Ubuntu boxes than

[Neo4j] Re: BadStatusLine with py2neo on CentOS6.4

2014-04-05 Thread Nigel Small
You must move in different server circles to me as I see far more Ubuntu boxes than anything else :-) As always, though, I'm happy to review pull requests on py2neo to fix issues for the operating system(s) you're using. Cheers Nige On 5 April 2014 23:33, Alan Robertson wrote: > It's worth n

[Neo4j] Re: BadStatusLine with py2neo on CentOS6.4

2014-04-05 Thread Alan Robertson
It's worth noting that RHEL6 is probably the most popular Linux server out there, and RHEL7 isn't out yet... I appreciate the difficulty, and I don't want to support it either. Unfortunately, as a practical matter, it seems that it's not something I'll likely be able to avoid... On 04/05/2014

[Neo4j] Re: BadStatusLine with py2neo on CentOS6.4

2014-04-05 Thread Nigel Small
Hi Alan A *BadStatusLine* is generally an indication that the remote server has disconnected, normally due to a timeout. Py2neo will usually retry when it sees one of these but the handling isn't bullet-proof and may not work at all under Python 2.6. I don't know about Red Hat either - maybe it pr