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
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
The looks like a repository issue, or network filtering related. However the next screen shot makes it even more mysterious.
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.
Miracle happens, the strange problem mentioned below seems resolved it self now, after hours of troubleshoot and hair pulling.
I guess it was some network packet filtering issue on one of the ISP's routers.
Just for the record, the problem lasted over 25 hours, and we spent at least 3 hours trying to find the cause.
Have a good weekend everyone!
On 2/12/2017 12:47 AM, Frank Liu - Orite Group wrote:
|Free forum by Nabble||Edit this page|