Re: [viewvc-users] The root 'XXX' was not found in the commit database

On 01/16/2013 07:57 PM, Dan Peterson wrote:
> When I click on the "Query revision history" link I receive the following
> error:
> 
> The root 'XXX' was not found in the commit database
> 
> What does this error mean and how do I fix it?

In the general sense, it means that ViewVC was unable to locate a row in the
commitsdb `repositories' table keyed on the path that viewvc.conf says is
associated with the 'XXX' rootname.

> For some background...
> 
> I have 80+ SVN repositories configured with ViewVC (1.0.7) and most of
> them work fine... I say most, because the Query form doesn't work with a
> few of them.
> 
> I looked in the ViewVC mysql DB in the repositories table and found a few
> repos were missing... turns out the missing ones are the same ones where
> the Query form doesn't work.   So... I decided to run the svndbadmin
> rebuild command on one of the repos to see if it would add it to the DB.
> I received this error:
> 
> Expected FS format between '1' and '3'; found format '4'
> 
> It was then I realized most of the repos were created with SVN 1.5, but
> some of the newest with SVN 1.6.  The libraries used with the ViewVC
> instance are for Subversion 1.5, which I'm *guessing* is why the Query
> form doesn't work.

Hrm...  I would think that if ViewVC was having trouble with the FS format
of your newer repositories, that would manifest universally:  that even
simply browsing those repositories in the ViewVC interface would not work.
Is this the case?

> Upgrading ViewVC and/or the SVN libs used by ViewVC isn't an option for a
> variety of unrelated reasons, so instead I decided to try and downgrade
> the version of the SVN repository DB format.   I did an "svn dump" of one
> of the 1.6 repos, then created a new repo (different name) using
> "svnadmin create --pre-1.6-compatible", and then loaded the dump file
> into this new repo.
> 
> I configured it in the viewvc.conf file and ran svndbadmin rebuild, which
> took about 10 mins with no errors.   I looked in the repositories table
> and sure enough the new repo was there.   Problem is, I'm still seeing
> the same problem when I click on the Query form link for the new
> (downgraded) repo.
> 
> So what's the problem?

When you examined the repositories table, did you find that the path name
associated with the repository was formatted consistently with the other
(working) repositories?  I mean, ViewVC tries to normalize those things, but...

Any chance your browser cache was getting in the way of seeing the form?

Sorry -- if it seems I'm groping in the dark a bit, it's because from what
I've read, you've taken the proper steps to remedy the problem.  Running
ViewVC atop Subversion 1.5 while apparently hosting your Subversion service
proper on 1.6 seems like a bit of a recipe for continual irritation, but
nothing stands out as a showstopper.  And certainly if your other
repositories are browsing and querying just fine ... well, that just defies
explanation.

-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=3044165

To unsubscribe from this discussion, e-mail: [[email protected]].

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJQ+BBHAAoJEPXg8AH+aBMzyfYP/0dQR/fnqjdLc23r5AXYWOgF
lvqJUOV3ppjCS31mIxh78orKNac+AEOi9qjo+Nr4KAsdhcWWvP6JJA+T3ZmxtDG5
Ve2gDi1uHunr5AIiKtxEETlm2n4vXuVLkSkLM6Db7CayTF/1CKcgabbZyNwKWU09
fK0ogfV/m9Of14znI56gnGNcj3vMuudbaNM6cwN63eLNqhe6ZJu31qLuE+Yh+h3Z
Gyz+AXc1DDntD2z63LaJ84JEzVlwNdW39iEMAUKNNq33VyhoXpkX4+rDXhF1Eh7L
jKvP35SplHB/ACYEmVQNVd2ZffCd/zBjZF6w7YFp/cAUEvGqRzxWmI50kHp5oPRL
MQrwgq+bjVwoBIfT7W8T5G+82jlPzYJ/yLlNkTqovGuJ81K7J7uINve5ZBqD0KIp
nU3sgRp4n2j5cHK/ep1C3emSxroU1sk03wlLreeZ95wOy78J+KZkBJd5xYMCqfmu
qPr7jiTY/AeQxEBqqr7TNgvvQSd178zUqL0IIoH0iMjaggaDC1Ad3xt6Hb6YAUGc
GEC5LpPbfwq4lEOLE7G34XocWyHjm35CnWiLhLA/61HlScaopX0JW2vnfgaOSAL4
e5wZxUX6fHG91ybtg00mKjBzkX2JLj7tMvNVKu8/gEk1BaGUFBbIf2HtkRbV4yNV
TmI5b8biLlYdOOBK/RXw
=a9Ce
-----END PGP SIGNATURE-----