Revision Graph can't be built

56 views
Skip to first unread message

gker...@gmail.com

unread,
Jan 21, 2020, 10:32:10 AM1/21/20
to TortoiseSVN
Hello,

I want to describe an observation which occurs since about two weeks ago (previously there was no problem, not sure what caused it to appear):

TortoiseSVN version is 1.13.1 for 64bit
SVN version is 1.7.4

When trying to retrieve the revision graph from a repository (about 12000 revisions) I'm first told that it takes about one hour. When there are finally only 10 revisions to retrieve, nothing is proceeding anymore. After a while I'm being told that the communication to the server is lost.

Here are the last lines from Wireshark:

Capture.PNG

I don't have this problem with smaller repositories.
Same problem with a 1.12. version of TortoiseSVN.

Any help would be appreciated, thanks!

Gernot

Stefan

unread,
Jan 21, 2020, 2:14:15 PM1/21/20
to TortoiseSVN
try clearing the log cache (settings dialog, saved data page).

gker...@gmail.com

unread,
Jan 22, 2020, 9:16:26 AM1/22/20
to TortoiseSVN
Hi Stefan,

thank you very much for the answer!

I got to the 'Saved Data' page and cleared 'Log messages (Input dialog)' and 'Log messages (Show log dialog)'.
Tried again to retrieve the Revision Graph. Unfortunately, the problem is still there...

Furthermore, the same problem happens on different client hosts with different TortoiseSVN versions so this seems to be a SVN server (or server host) issue. Something must have changed there since it worked before.

Br,
gernot

gker...@gmail.com

unread,
Jan 23, 2020, 4:12:53 AM1/23/20
to TortoiseSVN
Additional Info:
TortoiseSVN reports a problem contacting the server with error being "Connection timed out". So it seems it is waiting for info which is not coming from the server. This happens when only about 10 of the 12000 revisions to retrieve are still missing.

gernot

Niemann, Hartmut

unread,
Jan 23, 2020, 6:56:05 AM1/23/20
to TortoiseSVN

I had a similar (?) problem recently.

I had a large repo with more than 100 000 files, and I would create an overflow when I tried to update other than “full” because there seems to be a list of files sent

as one request, and the server has a size limit for this type of requests. I could update only in parts.

If the revision graph routine requests the full log, the reply can not be split into parts and the reply size is limited to x MBytes, one day the log will exceed that and will be truncated or not sent at all?

 

Hartmut

--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
tortoisesvn...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tortoisesvn/4b9b6292-e3aa-462d-a80a-566adabd19ac%40googlegroups.com.

gker...@gmail.com

unread,
Feb 21, 2020, 11:36:12 AM2/21/20
to TortoiseSVN

I'm still suffering from this problem.
To analyze it, I have opened Wireshark to see the network traffic to/from the SVN server which is going over Apache.

When I type "svn log" in a command prompt then i will get all logs. They are coming in chunks some 5 or 10 seconds apart (is this normal?) and this can be seen also in Wireshark.

When trying to show the revision graph from TortoiseSVN there is some traffic observable in Wireshark in the beginning but then nothing is coming until the connection timed out.

Does TortoiseSVN issue the "svn log" command to retrieve the info for the revision graph? Is it possible to make the request string from TortoiseSVN to the server visible? In DebugView i can see "CSVNLogQuery::Log(line 412) svn_client_log5". I would assume in Wireshark I can't see the request as it is a TLS connection.

Stefan

unread,
Feb 22, 2020, 2:54:15 AM2/22/20
to TortoiseSVN


On Friday, February 21, 2020 at 5:36:12 PM UTC+1, (unknown) wrote:

I'm still suffering from this problem.
To analyze it, I have opened Wireshark to see the network traffic to/from the SVN server which is going over Apache.

When I type "svn log" in a command prompt then i will get all logs. They are coming in chunks some 5 or 10 seconds apart (is this normal?) and this can be seen also in Wireshark.

no, that's not normal. This means you have serious network issues here. Most likely some virus scanner/firewall...
 

When trying to show the revision graph from TortoiseSVN there is some traffic observable in Wireshark in the beginning but then nothing is coming until the connection timed out.

So it really is a networking issue.
 

Does TortoiseSVN issue the "svn log" command to retrieve the info for the revision graph? Is it possible to make the request string from TortoiseSVN to the server visible? In DebugView i can see "CSVNLogQuery::Log(line 412) svn_client_log5". I would assume in Wireshark I can't see the request as it is a TLS connection.

The revision graph is basically an "svn log" (several calls usually, because it only fetches the logs entries that are not yet in the log cache), and then using that log info to create the graph.
The entry you see in dbgview is the info that the svn API to fetch the log is called, that's the same as 'svn log' does.

 If you're sure it's not a virus scanner/firewall issue (but make absolutely sure first!), then you could try tinkering with your server setup: disable nagle algorithm (TCP_NODELAY), increase the keepalive, ...

But from my experience I would bet that it's a virus scanner and/or firewall...

gker...@gmail.com

unread,
Feb 24, 2020, 4:22:17 AM2/24/20
to TortoiseSVN
I don't think it is a firewall issue since both client and server are on the same domain and the domain firewall is not activated.

As i'm able to get the logs with "svn log": Is there a possibility to save the retrieved log into a file and let TortoiseSVN read this log and build the revision graph out of it?

Thanks,
gernot

gker...@gmail.com

unread,
Feb 24, 2020, 4:49:04 AM2/24/20
to TortoiseSVN
Another Info:

I already mentioned that the "svn log" output is coming in 'cuncks' some seconds apart.
I now tried another svn command: "svn info -R". There the output is whizzing by very fast. So the 'cuncking' info seems to be special to the "svn log" command. Maybe the server just needs time to process the output?

Thanks,
gernot
Reply all
Reply to author
Forward
0 new messages