Sean Russell <ser@germane-software.com> writes:
> On Wednesday 19 December 2001 12:21 pm, Ben Collins-Sussman wrote:
> > Sean Russell <ser@germane-software.com> writes:
> > > Anyway, copy has never worked for me; I've added the ServerName directive
> > > to the httpd.conf file, to no avail. The server error logs report:
> ...
> > Odd. What is the repos->repos command you're sending?
>
> svn cp http://.../rexml/trunk http://.../rexml/tags/1.2.3
Okay, we'll have to continue this thread. I have no ideas yet. :-)
>
> > > More critical is that subversion just mysteriously stopped working, after
> > > I finally got the repository version compiled and running today. I
> ...
> > Try this: stop apache; change into the repository's 'db' subdirectory;
> > run '/usr/local/BerkeleyDB.3.3/bin/db_recover -ve'; restart apache.
>
> I moved the old repository, created a new one, and re-imported my projects,
> and it seems to be working. I also did your db_recover on the old
> repository, and now it works, too. Thanks! I'll stick that in the tutorial.
>
For some reason, we've noticed that a DB environment has the potential
to get 'wedged' every once in a while, and needs to be 'unwedged' by
the db_recover utility.
It seems to happen if a DB-using application ever suddenly dies, or if
you interrupt it with a signal. It's not perfectly reproducible, so
we've not done a lot of investigation into the problem. But
*sometimes* we can reproduce it by simply running 'svnadmin lsrevs
repo', and then hitting control-c. Really weird.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:53 2006