On 7/1/13 9:52 AM, "Joshua Ladd" <josh...@mellanox.com> wrote:
>I think we (MLNX) are getting corrupted/truncated checkouts. Lately, I >have been running into the following error on our internal systems when >doing a secure checkout: > >svn co https://svn.open-mpi.org/svn/ompi/trunk ompi-trunk > >svn: E175002: REPORT of '/svn/ompi/!svn/vcc/default': Could not read >response body: Secure connection truncated (https://svn.open-mpi.org) > >Googling around, seems like a problem with our SVN server timing out. Has >anyone in the community seen this before? We (at Sandia) see this all the time. Our proxy server gets overloaded (or bored, hard to tell) and drops the persistent connection SVN creates with the Apache server at IU. SVN doesn't try to re-establish the connection once it drops, so it aborts. I've never had a case where svn up (or multiple svn ups) in the checkout didn't resolve the problem eventually. Brian -- Brian W. Barrett Scalable System Software Group Sandia National Laboratories
smime.p7s
Description: S/MIME cryptographic signature
