On Wed, Sep 11, 2013 at 6:51 PM, Philip Martin <philip.mar...@wandisco.com> wrote: > Curt Sellmer <sellmer...@gmail.com> writes: > >> On Wed, Sep 11, 2013 at 2:46 PM, Ben Reser <b...@reser.org> wrote: >>> On 9/11/13 12:24 PM, Curt Sellmer wrote: >>>> Here is a tail of the error.log. This is from when I was running the >>>> tests earlier. >>>> I was hoping to pinpoint which set of log messages corresponded to >>>> each error, but of >>>> course I cannot get it to fail at all right now. I'll keep trying >>>> throughout the day. >>> >>> Based on the error messages you've been posting I'd suggest that you run >>> svnadmin verify on your repository. >>> >> >> I just ran svnadmin verify on the repo again and still it does not >> report any errors. > > You said you dumped and loaded your repository. You also have > corruption shown by apache that is not shown by svnadmin. When you > dump/load are you also putting the new repository in the same place as > the old repository? If so, are you restarting apache? It's perfectly > acceptable to replace a repository but you must restart apache if the > repository is altered but the UUID is not changed. > > -- > Philip Martin | Subversion Committer > WANdisco // *Non-Stop Data*
In this case I created a new repo using a different name. I left the old one intact. Then just referenced the new repo's url. In the last few days, thought I have moved the old repo to A.orig then moved the new repo to A. I did not know of the requirement to restart apache. Will do that going forward. Thanks.
