I am facing same problem. Did you find any solution ?
Eric Hoch-3 wrote:
> -----Original Message-----
> From: Ryan Schmidt [mailto:subversion-2008c_at_ryandesign.com]
> Sent: Monday, November 03, 2008 6:02 PM
> To: Eric Hoch
> Cc: users_at_subversion.tigris.org
> Subject: Re: Empty log / error on TortoiseSVN
> On Nov 3, 2008, at 16:29, Eric Hoch wrote:
>>> I'm having a problem with our internally hosted
>>> repository. We're running svnserve 1.5 (1.5.1 I think) on Windows,
>>> and have been running with little or no problems for ~3 years.
>>> Obviously we were running earlier versions in the past, and have
>>> been running 1.5 since shortly after its release. The repository
>>> currently has ~19500 revisions in it. On the client end, we're
>>> running the latest version of TortoiseSVN (1.5.5, Build 14361), and
>>> occasionally the svn command-line client (1.5.0).
>>> The problem I'm experiencing is that whenever I
>>> attempt to view the log for any part of the repository, TortoiseSVN
>>> is reporting the following message: "There has been a problem
>>> connecting the server. Do you want to see the cached data instead?"
>>> "Please understand that the cached data may be outdated, incomplete
>>> or even misleading due to incomplete history." Along with the
>>> options to go "Offline for now", "Permanently offline" and "Don't
>>> go offline", plus a check box to make that selection the default.
>>> This is a persistent problem, happening every time I attempt to
>>> view the log. If I turn off log caching, or select "Don't go
>>> offline", I get the error dialog which simply states: "C:\Projects
>>> \subversion-1.5.1\subversion\libsvn_repos\log.c" with no additional
>>> information. If I attempt a "svn log" from the command-line, I can
>>>> get log entries returned from the server, but each entry is
>>> effectively empty, aside from the revision number.
>>> How do I begin to troubleshoot this problem?
>> It sounds like the log information in your revisions is empty.
>> Did people actually enter log messages when committing? If so, were
>> you able to see them with "svn log" before? How long ago? Was that
>> before you updated to 1.5?
>> You could check the files in the revprops directory in the db
>> directory in your repository directory on the server. Do they have
>> the log messages in them?
> Hello Ryan,
> Thanks for the reply. There definitely should be log messages
> for every revision, as I have a hook script in place to ensure that. In
> addition, I am not able to see any log information for revisions I was
> previously able to. Also note that it is not just the log message that
> is missing, but the author and date/time information as well. The only
> information I can see in the log at this point is the revision number.
> This was working early last week, so there must have been some change
> last week that caused this problem. There were no changes to the server
> configuration last week to the best of my knowledge. I did ask our
> administrator for a dump, and then a copy of the repository, but I'm
> fairly confident that he was not doing those activities when the
> behavior started.
> I'll take a look at the files in the revprops directory to see
> if it leads anywhere.
> -Eric Hoch
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
View this message in context: http://www.nabble.com/Empty-log---error-on-TortoiseSVN-tp20312432p24529373.html
Sent from the Subversion Users mailing list archive at Nabble.com.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-17 08:45:39 CEST