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 On Monday, February 24, 2020 at 10:22:17 AM UTC+1, gernot kerschbaumer wrote: > > 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 > > On Saturday, February 22, 2020 at 8:54:15 AM UTC+1, Stefan wrote: >> >> >> >> 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... >> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/c130b9e0-9d70-43b7-a04d-85ecad6218d6%40googlegroups.com.
