On Fri, Jul 08, 2005 at 01:45:30PM -0400, R. Scott Bailey wrote: > I don't know if this is an actual bug, or just user stupidity. :-) I > haven't done a lot of playing with onak, but decided to exercise it a > little bit by loading it with the debian keyring: > > gpg --export --keyring /usr/share/keyrings/debian-keyring.gpg \ > | onak -b add > > This worked without errors, reporting 902 new keys loaded, and my first > lookup worked. (An index search on "brandon" if it matters...) > > After that, every single access attempt dies with "Illegal instruction" > on stdout and the message "Error opening db environment: /var/lib/onak > (DB_RUNRECOVERY: Fatal error, run database recovery)" in > /var/log/onak.log. :-(
Hmmm. Berkeley DB seems to be very fragile; if onak exits uncleanly for any reason it can get unhappy. I have code for a backend DB daemon that's talked to over a unix socket to try and limit this in future versions. Try a "db4.2_recover -v" (this is in the db4.2-util package) and see if that fixes things for you? > I have no clue how to perform the required recovery and can't find > anything in the man page, the READMEs, or Google. The documentation is lacking; I'll have to add something about this to it if it sorts your problem out. J. -- /-\ | A fool and his money are SYSOP |@/ Debian GNU/Linux Developer | material. \- | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
