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

Re: could not connect to server

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-05-04 20:28:41 CEST

solo turn <soloturn99@yahoo.com> writes:

> svn is still unusable over slow line.

Well, yes, there you go! I was just thinking to myself, "gee, I
wonder if subversion is usable over slow lines; I wonder if it makes
efficient use of the network."

But that error below -- "could not connect to server" -- that says it
all! I guess subversion is unusable, over slow lines in particular.
Thanks for clearing that up. ;-)

> A svn/packages/win32-innosetup/templates/svn-doc.css
> svn: RA layer request failed
> svn: could not checkout a file
> svn: GET of
> /repos/svn/!svn/bc/5798/trunk/packages/win32-innosetup/templates/svn
> -doc.css: could not connect to server

This is a TCP/IP error, not a subversion bug. Neon is telling you
that it actually failed to open a socket to the server.

Try pinging the server, see if you're getting erratic ping times, or
unexpectedly long delays. The problem here is network connectivity.
I know there's no http proxy, but there's most likely -something-
wrong along the IP route to the host, like a flakey ISP.

> should not error messages be more like "could not connect to server
> in blabla()" to give an exact position in the code?

Yes. If you had compiled with --enable-maintainer-mode, you would
have seen an exact position in the code printed out.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 4 20:30:33 2003

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

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