Thanks John! I tried running db_upgrade, but apparently the utilities were
not included in my setup. So I ran the following:
gomez@gwnma:/var/www/nd/t1$ sudo apt-get install db4.8-util
That installed the utilities, but I'm still having some trouble:
gomez@gwnma:/var/www/nd/t1$ sudo
Try removing the environment files before you upgrade (or after if
you didn't save the old file). When I released that version of NOID
I have since regretted leaving in code that created a stub environment
(that actually isn't used by NOID) because it just creates upgrade
problems that I never
That didn't work either. I started with a fresh copy of the NOID directory
from before I tried the upgrade command:
gomez@gwnma:/var/www/nd/t1$ ls NOID
__db.001 __db.003 __db.005 lock log.01 noid.bdb
__db.002 __db.004 __db.006 log logbdb README
Sounds good. At this distance and given my focus on a new NOID release
(that separates minting from binding in separate databases and simplifies
installation by relying only on the standard DB_File), I don't think I
can help you devise a better strategy than the one you've come up with.
-John
Does anyone here have expertise with Berkeley DB?
I was running an instance of NOID (which uses Berkeley DB) to mint and
resolve ARKs. I updated the OS for the server it was running on from
Ubuntu 9 to Ubuntu 10. Now NOID has stopped working and complains that the
db version doesn't match:
The standard BerkeleyDB library probably changed when you upgraded
Ubuntu, and it complains that the NOID database (written with the old
library) is incompatible.
You should be able to use db_upgrade to convert the NOID database
(NOID/noid.bdb). db_upgrade is a command line utility that comes
