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

"Can't write to connection: An existing connection was forcibly closed"

From: V.S. <john_v_doe_at_yahoo.com>
Date: 2006-01-03 18:01:59 CET

Hi, all.

Lately I've encountered a persistent and very worrying issue with SVN.
Namely, a relatively modest commit to a very modest repository
repeatedly failed with a message : "svn: Commit failed (details
follow): svn: Can't write to connection: An existing connection was
forcibly closed by the remote host.

The commit in question had about 143 files involved total, about 77
of those changed, about 66 added. The working copy in question has
about 1000 files in less than 100 dirs for a total of about 42MB -
all this excluding SVN related files, of course. The SVN server was
running on a Debian box, serving with svnserve (originally v1.1.4).
The client was running both TortoiseSVN (at first) and then vanilla
svn on a WinXP machine. Both client and server were sitting on the
same LAN, a mere switch away from one another. The repository has
been up for over 3 months with over 100 commits to it, and no other
problems observed so far.

After several failed attempts of doing this with TortoiseSVN against
v1.1.4 svnserve, I attempted to pull this off with vanilla svn cmdline
client, getting identical results. I then tried upgrading the server
to v1.2.3 and trying again with both Tortoise and vanilla svn - to
no avail. The client would always stall for about a minute after some
file during the "send to server" portion of the commit, and then
report the dreaded "Can't write to connection..." message.

Eventually, I had to break up the commit into no less than SEVEN
separate commits before I could commit all the changes in question.
Every time I would first commit one of the remaining subdirs, then
try to commit all the other remaining subdirs in one go, and when
that failed - commit one of the remaining dirs alone.

I did a search for the error message in question on the mailing list
but found no solution whatsoever. In fact, the couple of messages from
people who seem to have encountered situation similar to mine were left

Does anyone have any idea what's going on? Any help would be greatly

Thanks in advance,

V. Solo.

Server :
Debian Sarge.
Subversion v1.1.4 (1.1.4-2) & v1.2.3 (1.2.3dfsg1-3).
Serving with svnserve.
FSFS repository.

Client :
WinXP Pro, SP2.
Subversion 1.2.3 (r15833) & TortoiseSVN 1.2.6, Build 4786

svn client output :
x:\foo\bar>svn commit --file LogMsg.txt
Sending Foo\Bar1.cpp
Sending Bar\Foo1.cpp
Sending Bar\Foo1.h
    <about 137 more lines of messages>
Adding Foo Bar\Baz\__Baz1.xml
Adding Foo Bar\Baz1.xml
Adding Foo Bar\Baz2.xml
Transmitting file data
Commit failed (details follow):
svn: Can't write to connection: An existing connection was forcibly
closed by the remote host.


Yahoo! for Good - Make a difference this year.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 3 18:10:52 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.