[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Berkeley DB problem: "Could not allocate memory"

From: Nicolás Lichtmaier <nick_at_panoptico.reloco.com.ar>
Date: 2005-02-07 23:31:53 CET

I'm having trouble with subversion. Some large commits fail with:

[Mon Feb 07 19:00:06 2005] [error] [client 10.53.3.67] (20014)Error
string not specified yet: Berkeley
DB error while opening 'uuids' table for filesystem
/var/lib/svn/pv/db:\nCannot allocate memory
[Mon Feb 07 19:00:06 2005] [error] [client 10.53.3.67] Could not fetch
resource information. [500, #0]
[Mon Feb 07 19:00:06 2005] [error] [client 10.53.3.67] Could not open
the requested SVN filesystem [50
0, #160029]
[Mon Feb 07 19:00:06 2005] [error] [client 10.53.3.67] Could not open
the requested SVN filesystem [50
0, #160029]

Is there anything I can do to help debug this problem. Should I rebuild
subversion with --enable-maintainer-mode ? Is that option ok for a
production server?

I've tried increading the "cache", as was said in a previous thread in
this mailing list, by adding "set_cachesize 0 8388608 1" to db/DB_CONFIG
and running "svnadmin recover". According to the users the problem only
got worse.

This is fairly big repository:

-rw-r--r-- 1 apache root 18M feb 7 19:19 representations
-rw-r--r-- 1 apache root 27M feb 7 19:19 nodes
-rw-r--r-- 1 apache root 30M feb 7 19:19 changes
-rw-r--r-- 1 apache root 5.3G feb 7 19:19 strings

I'm using versión 1.1.3 (r12730). The system is RedHat AS 3.

Thanks for any help you can give me.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 7 23:33:16 2005

This is an archived mail posted to the Subversion Dev mailing list.