Frank Liu - Orite Group
2017-12-01 13:47:12 UTC
Hi There
We had a really strange issue with subversion.
The server side is running on Linux with svnserve daemon on the default
svn port tcp 3690, with latest stable version 1.9.7
We have clients on both Linux and Windows (TortoiseSVN), all of them are
on version 1.9.7 as well.
The issue started with one of the the repository on a Linux client were
not able to commit, with connection timed out. However committing from
Windows client to the same repository is fine, and updating the working
copy from repository is also fine for both Linux and Windows clients.
Today I have conducted more tests trying to find the cause of the
problem, but with not much luck.
Following is a screens shot is from a Linux client, when we trying to
list content from remote SVN repository directories
* first directory listing works fine
* but the second directory got connection timed out
* it's no even showing the authentication step
* hangs for about 5-10 minutes before seeing the connection timed out
message
* this observation is not occasional, we have tried at least 10 time,
on different location, and different Linux client machine, all
result the same
The looks like a repository issue, or network filtering related. However
the next screen shot makes it even more mysterious.
* this test is carried out on a Windows TortoiseSVN clientrunning
version 1.9.7
* it's on the same local network as the previous Linux client
* it lists the exact same directory as the previous test with no
problem at all
On other Linux client test of the same repository, we also got timed out
on update and commit actions on certain directories, however all tests
from Windows client are successful.
We have done few other tests including disabling firewalls, check tcp
dumps, enable server logs on svnserve, but couldn't find anything useful.
We've been running SVN since 1.1, this is the first major instance we've
ever faced, and haven't had a clue about.
Thanks for reading so far. It would be much appreciated if anyone could
shed some light on how to debug from clients or server for these kind of
wired connection issues to track down the root cause.
--
kind regards,
Frank Liu
Orite Group Pty Ltd
http://www.orite.com.au
e-mail: ***@orite.com
tel: +61(2) 8090 2030 ext. 100
fax: +61(2) 8212 9543
mob: 0414 583 962
We had a really strange issue with subversion.
The server side is running on Linux with svnserve daemon on the default
svn port tcp 3690, with latest stable version 1.9.7
We have clients on both Linux and Windows (TortoiseSVN), all of them are
on version 1.9.7 as well.
The issue started with one of the the repository on a Linux client were
not able to commit, with connection timed out. However committing from
Windows client to the same repository is fine, and updating the working
copy from repository is also fine for both Linux and Windows clients.
Today I have conducted more tests trying to find the cause of the
problem, but with not much luck.
Following is a screens shot is from a Linux client, when we trying to
list content from remote SVN repository directories
* first directory listing works fine
* but the second directory got connection timed out
* it's no even showing the authentication step
* hangs for about 5-10 minutes before seeing the connection timed out
message
* this observation is not occasional, we have tried at least 10 time,
on different location, and different Linux client machine, all
result the same
The looks like a repository issue, or network filtering related. However
the next screen shot makes it even more mysterious.
* this test is carried out on a Windows TortoiseSVN clientrunning
version 1.9.7
* it's on the same local network as the previous Linux client
* it lists the exact same directory as the previous test with no
problem at all
On other Linux client test of the same repository, we also got timed out
on update and commit actions on certain directories, however all tests
from Windows client are successful.
We have done few other tests including disabling firewalls, check tcp
dumps, enable server logs on svnserve, but couldn't find anything useful.
We've been running SVN since 1.1, this is the first major instance we've
ever faced, and haven't had a clue about.
Thanks for reading so far. It would be much appreciated if anyone could
shed some light on how to debug from clients or server for these kind of
wired connection issues to track down the root cause.
--
kind regards,
Frank Liu
Orite Group Pty Ltd
http://www.orite.com.au
e-mail: ***@orite.com
tel: +61(2) 8090 2030 ext. 100
fax: +61(2) 8212 9543
mob: 0414 583 962