The recent svn.collab.net woes might be due to problems we've seen in
the past where ViewCVS does something that uses up too many Berkeley
locks. This is consistent with the "Cannot allocate memory" error,
which is something we've seen from Berkeley.
Ben recovered the repository, in response to this thread, and things
seem to be fine now (except that this problem may recur). Commit
emails are working again, too.
-Karl
Markus.Theilen@t-online.de (Markus Theilen) writes:
> Erik Huelsmann wrote:
>
> > Trying to update, I get the "Can't open filesystem" error.
> > bye,
> > Erik.
> >
>
> Hi!
>
> Seems that the Berkeley DB can't allocate memory for its operations on
> the file system.
>
> This is what I get when I try the viewcvs from svn.collab.net:
>
> Python Traceback
>
> Traceback (most recent call last):
> File "/usr/local/viewcvs-1.0-dev/lib/viewcvs.py", line 2585, in main
> request.run_viewcvs()
> File "/usr/local/viewcvs-1.0-dev/lib/viewcvs.py", line 263, in
> run_viewcvs
> self.rootpath, rev)
> File "/usr/local/viewcvs-1.0-dev/lib/vclib/svn/__init__.py", line
> 279, in __init__
> self.repos = repos.svn_repos_open(rootpath, self.pool)
> SubversionException: ("Berkeley DB error while opening 'copies' table
> for filesystem /usr/www/repositories/svn/db:\nCannot allocate memory",
> 160029)
>
> Regards,
> Markus
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 26 19:32:18 2004