369399 - SVN connections reset frequently

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Michael Morgan [:morgamic]]

Connections to SVN seem to reset often.  When trying to commit, update or perform any other command that requires communication with the server, SVN often fails on the first try then works on the very next try without a problem.  This happens on servers inside or outside of the MPT VPN.

Comment 1

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

Might be worth checking the logs on the svn server; could be a DNS server timing out (but returning the result later, so it's cached and fast on the next request).

Comment 2

[Aravind Gottipati [:aravind]]

This failing on the first attempt and succeeding on the second, does this happen sporadically or every single time you connect to svn?

Comment 3

[Reed Loden [:reed]]

Sporadically for me, at least, as I see this issue, too.

Comment 4

[Justin Scott [:fligtar]]

For me, it's almost every time when trying to update. Commits usually work fine, but occasionally they have the problem too.

Comment 5

[Aravind Gottipati [:aravind]]

We had some dns issues with MPT that may have been causing this problem.  We fixed those last week.  Let me know if you continue to notice these timeouts/failures.

Comment 6

[Justin Scott [:fligtar]]

They have been far less frequent since the bug was originally filed, however I do still have this happen sometimes.

Comment 7

[Wil Clouser [:clouserw]]

I've had it happen to me twice over the past couple of days, which is a lot less than usual.  I was going to try making all my commands verbose, so when something happened I might be able to help track it down, but SVN saw me coming:

  wclouser@khan-vm:~/public_html/remora$ svn up -v
  Subcommand 'update' doesn't accept option '-v [--verbose]'

Comment 8

[Wil Clouser [:clouserw]]

On a suggestion from aravind, I added 10.2.74.16 to the hosts file on khan, and svn commands from khan have been doing great.

Comment 9

[Aravind Gottipati [:aravind]]

For those without access to the VPN, use 63.245.208.183 for the svn ip address.  This bypasses the NS and goes straight to the host.

Comment 10

[matthew zeier [:mrz]]

svn.mozilla.org now goes to 63.245.208.183 which should resolve whatever connectivity issues you were seeing.  

Comment 11

[Aravind Gottipati [:aravind]]

separated svn from the NS, so connections are now going straight to the primary svn server.  Please re-open if you continue to notice any problems with it.