SVN Down and Nightly Builds
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2006 05:29 PM
I just wanted to let you folks know that your SVN has been down for a little while on 04/26/06 2:22 PM PST
here is the error when I tried to do an update
ubuntu-gautham:~/projects-alfresco/alfresco1.2/root$ svn up
svn: Berkeley DB error while opening 'uuids' table for filesystem /home/svnadmin/svn/alfresco-open/db:
Cannot allocate memory
svn: bdb: Lock table is out of available locker entries
svn co svn://www.alfresco.org/alfresco/HEAD
also yeilded similar results and my colleague also faced similar problems on windows(tortoise)
Also, we are working on a client project, and noticed that you have not updated your nightly builds recently. The reason I mention this, is that we want to have some of the newer features, such as multiple values for metadata properties, but cannot tell our client that we are working off an svn checkout. That is, we would rather have a "recent" nightly build that we can refer to as our base platform for customizations.
Thanks–Gautham Hegde
here is the error when I tried to do an update
ubuntu-gautham:~/projects-alfresco/alfresco1.2/root$ svn up
svn: Berkeley DB error while opening 'uuids' table for filesystem /home/svnadmin/svn/alfresco-open/db:
Cannot allocate memory
svn: bdb: Lock table is out of available locker entries
svn co svn://www.alfresco.org/alfresco/HEAD
also yeilded similar results and my colleague also faced similar problems on windows(tortoise)
Also, we are working on a client project, and noticed that you have not updated your nightly builds recently. The reason I mention this, is that we want to have some of the newer features, such as multiple values for metadata properties, but cannot tell our client that we are working off an svn checkout. That is, we would rather have a "recent" nightly build that we can refer to as our base platform for customizations.
Thanks–Gautham Hegde
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2006 06:08 PM
from reading around and poking in our own svn I found these tidbits from the google gods related to your svn errors
increase the locker entries in /path/to/repository/db/DB_CONFIG
convert to fsfs instead of bdb
$ svnadmin create –fs-type fsfs /path/to/new/repository
$ svnadmin dump /path/to/repository | svnadmin load /path/to/new/repository
<jamest>i guess we outgrew the berkley db settings for subversion
<jamest>so I had to bump the #s up for the logs
<jamest>In a different test repository when I had this problem I bumped up the
<jamest> DB_CONFIG values to look like this:
<jamest>set_cachesize 0 8388608 8
<jamest> set_lg_regionmax 524288
<jamest> set_lg_bsize 2097152
<jamest> set_lg_max 8388608
increase the locker entries in /path/to/repository/db/DB_CONFIG
convert to fsfs instead of bdb
$ svnadmin create –fs-type fsfs /path/to/new/repository
$ svnadmin dump /path/to/repository | svnadmin load /path/to/new/repository
<jamest>i guess we outgrew the berkley db settings for subversion
<jamest>so I had to bump the #s up for the logs
<jamest>In a different test repository when I had this problem I bumped up the
<jamest> DB_CONFIG values to look like this:
<jamest>set_cachesize 0 8388608 8
<jamest> set_lg_regionmax 524288
<jamest> set_lg_bsize 2097152
<jamest> set_lg_max 8388608
