Return-Path: Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: (qmail 91785 invoked from network); 20 Oct 2010 18:23:11 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Oct 2010 18:23:11 -0000 Received: (qmail 4976 invoked by uid 500); 20 Oct 2010 18:23:11 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 4942 invoked by uid 500); 20 Oct 2010 18:23:11 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 4935 invoked by uid 99); 20 Oct 2010 18:23:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Oct 2010 18:23:10 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=MSGID_MULTIPLE_AT,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [12.108.173.117] (HELO bil.konicaminolta.us) (12.108.173.117) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Oct 2010 18:23:02 +0000 Received: from [10.16.43.100] (account shaun.pinney HELO SHAUNOPTI745) by bil.konicaminolta.us (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 5236126; Wed, 20 Oct 2010 11:22:40 -0700 From: "Shaun Pinney" To: "'Shaun Pinney'" , References: <025f01cb6f43$aec1a790$0c44f6b0$@pinney@bil.konicaminolta.us> In-Reply-To: <025f01cb6f43$aec1a790$0c44f6b0$@pinney@bil.konicaminolta.us> Subject: RE: Users cannot reliably view SVN log messages remotely Date: Wed, 20 Oct 2010 11:21:02 -0700 Message-ID: <003701cb7083$8d8918b0$a89b4a10$@pinney@bil.konicaminolta.us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 thread-index: ActvQ65wRWazCCyWROSJ5pLi76IMkABPa73g Content-Language: en-us X-Virus-Checked: Checked by ClamAV on apache.org I got past the issue and wanted to post my solution here for other SVN admins/users. HTH. > I've got a distant user who cannot reliably view the SVN log messages > Using TortoiseSVN. If he 'refreshes', he can view the SVN log messages > fine. Also, checkouts work fine. Other users at his (distant) site > seem to have the same issue, but I can't reproduce the issue here and > haven't heard of similar issues from other sites. >From inspecting the Apache logs, I found that the user's client was in an invalid state. Somehow it was sending the server requests for revisions that did not modify any files in the selected directory. For example, Revision 2688 does not exist on Path/To/Directory, but this was in the access_log: "REPORT /svn//!svn/bc/2688/Path/To/Directory HTTP/1.1" 404 247 His TSVN client was also displaying revision 2689 in the Show Log windows. After asking the user to disable log caching and clear his saved data he was able to view the log messages again without clicking 'refresh' and the invalid revision 2689 disappeared from his TSVN window. > Provider encountered an error while streaming a REPORT response. [500, #0] > A failure occurred while driving the update report editor [500, #103] > Error writing base64 data: Software caused connection abort [500, #103] As for these other error messages, I'm still not sure the reason but there's no pressing need to investigate at the moment. If I find a solution later I'll make sure to post it here for everyone. Best, Shaun