[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Apache+mod_dav_svn gives me "Could not read status line" on COPY requests

From: Samuel Vogel <samydelux_at_gmail.com>
Date: Mon, 05 Oct 2009 19:35:48 +0200

Hey guys,

I've been seeing a strange problem now for over a month.

I tried to do the following setup:
Nginx on port 80 to serve all static & dynamic web content and Apache
with mod_dav_svn on port 81 for SVN access. Nginx was supposed to proxy
svn.domain.com to localhost:81, to give us a nice SVN url.
To eliminate nginx as an error source, I opened up Apache to the web on
port 81, so I am accessing svn.domain.com:81 right now.

Browsing the repository, updates and checkouts work fine. Even commits
work, but as soon as they include a COPY action the following happens:

# svn commit -m "Kohana 3 upload"
Authentication realm: <http://svn.domain.com:81> redmine
Password for 'samuel.vogel':
Sending application/bootstrap.php
Adding application/config/database.php
Sending index.php
Adding modules/product-web-www
svn: Commit failed (details follow):
svn: COPY of
'/project/!svn/bc/152/branches/kohana3/modules/product-web': Could not
read status line: connection was closed by server (http://svn.domain.com:81)

The Apache error log stays clean, but I captured the following tcpdump

It seems like there is simply no real response from Apache to the COPY
I couldn't find anything about this on google, so you guys are my last
resort to get this sorted out :)

The server and client both run Debian. Apache on the server runs on
Version 2.2.13 and SVN on both server and client are 1.6.4, all
installed from the debian repos.

Please let me know if I can provide any other useful info on this!



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-05 19:40:06 CEST

This is an archived mail posted to the Subversion Users mailing list.