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

svn: Connection closed unexpectedly

From: Matthew Yaconis <myaconis_at_nycap.rr.com>
Date: 2005-09-19 16:57:57 CEST

I have a software development project I'm working on that is usable in both
Win32 and Linux environments (primary environment is Linux).

Linux system (w/repository and running svnserve):
svn: 1.1.0 (using fsfs)

Windows system:
OS: WinXP professional
svn: 1.1.3
TortoiseSVN: 1.1.3

I've been successfully committing files and checking files out of my
repository on the Linux box for several months using the svnserve
instantiated by xinetd. However, after I did a commit using TortoiseSVN the
other day and now I can no longer do updates, commits, or "svn status -u"
anymore on the Linux machine. For some reason the TortoiseSVN client can
still connect and check out and commit.

Whenever running the svn commands on the Linux box I get the response:
"svn: Connection closed unexpectedly"

I immediately checked the permissions on the db directory and did a
"svnadmin recover" on the repository but that didn't fix anything.
Unfortunately, all the repositories on the Linux box are now inaccessible
via svnserve (I can check out files locally using "svn co
file:///repospath/repos"). I searched on "Connection closed unexpectedly"
and found one thread that spoke of path settings in the .bashrc but I don't
think that is my problem (since everything worked great for then stopped
immediately after a checkin from TortoiseSVN). Does anyone know what may
have happened or can anyone provide any advice?



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 19 17:00:03 2005

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.