svnserve selectively refusing connections from users?

[Nick Zitzmann <su...@spamgourmet.com>]

Until today we haven't had any problems with our users accessing our 
repositories, but now we have a user who for some reason can't connect. 
Until today, the user was able to access the repository. Now, when he 
tries to run "svn update" on an existing checkout, or"svn co" and point 
it to our Subversion server, he always gets a "connection refused" 
message:

svn: Can't connect to host 'Server.local': Connection refused

Oddly enough, "svn status" connects, but it gives the wrong output (it 
claims the server is at repository revision 1 when it's actually at 
revision 3, and doesn't say what has been changed since revision 1).

More details:

1. Both the client and server are running the latest production release 
of Mac OS X (10.3.4)
2. Both the client and server are running Subversion 1.0.5
3. The client and server are both on the local LAN
4. The server is running at the time as a background daemon
5. None of our other users are having this problem
6. I'm able to access the server just fine from the loopback device 
(localhost)
7. Deleting the user's ".subversion" directory in his home directory 
did not help
8. The user can connect to the server using SSH with no problems
9. We're using the plain old svn protocol, not svn+ssh or http
10. This worked until today, and I didn't mess with the software on my 
side

What do I have to do (or does the user have to do) to make it so this 
user can connect to the server again? Help?

Nick Zitzmann
<http://www.chronosnet.com/>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svnserve selectively refusing connections from users?

[Max Bowsher <ma...@ukf.net>]

Nick Zitzmann wrote:
> Until today we haven't had any problems with our users accessing our
> repositories, but now we have a user who for some reason can't connect.
> Until today, the user was able to access the repository. Now, when he
> tries to run "svn update" on an existing checkout, or"svn co" and point
> it to our Subversion server, he always gets a "connection refused"
> message:
>
> svn: Can't connect to host 'Server.local': Connection refused
>
> Oddly enough, "svn status" connects, but it gives the wrong output (it
> claims the server is at repository revision 1 when it's actually at
> revision 3, and doesn't say what has been changed since revision 1).

Do you mean "svn status -u" ? Plain "svn status" never contacts the
repository at all.

> More details:
>
> 1. Both the client and server are running the latest production release
> of Mac OS X (10.3.4)
> 2. Both the client and server are running Subversion 1.0.5
> 3. The client and server are both on the local LAN
> 4. The server is running at the time as a background daemon
> 5. None of our other users are having this problem
> 6. I'm able to access the server just fine from the loopback device
> (localhost)
> 7. Deleting the user's ".subversion" directory in his home directory
> did not help
> 8. The user can connect to the server using SSH with no problems
> 9. We're using the plain old svn protocol, not svn+ssh or http
> 10. This worked until today, and I didn't mess with the software on my
> side

Truly strange.

Can you telnet to the svn server? The svnserve port is 3690, and you should
get a greeting which looks like this:

( success ( 1 2 ( ANONYMOUS ) ( edit-pipeline ) ) )

and the connection should not be closed by the server until you press
Return/Enter.

Max.




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

[SOLVED] Re: svnserve selectively refusing connections from users? (subversion1: message 7 of 20)

[Nick Zitzmann <su...@spamgourmet.com>]

On Jul 16, 2004, at 9:30 AM, Nick Zitzmann wrote:

> svn: Can't connect to host 'Server.local': Connection refused

Never mind, already solved it: An entry in the user's computer's 
/etc/hosts was throwing off the user's connection by redirecting the 
user to the wrong address. For some reason svn didn't catch that, but 
the telnet client clued us in on that when we noticed it was forwarding 
to the wrong address.

It's always the little things!

Nick Zitzmann
<http://www.chronosnet.com/>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org