Package: sks Version: 1.1.3-1 After an upgrade to 1.1.3, a fully-populated keyserver hung when i searched it for the string "dkg".
looking at /var/log/sks/db.log, i see:
2012-06-25 01:12:55 Error fetching uid during VIndex for keyid
0xDB686C92D9D59F61: Bdb.DBError("unable to allocate memory for mutex; resize
mutex region")
the sks db process was hung in a futex() system call (according to
strace) and needed to be kill -9'ed to terminate.
Following John Clizbe's advice [0], i was able to get the system working
and able to respond to searches with:
## ensure sks is stopped
cp /usr/share/doc/sks/sampleConfig/DB_CONFIG /var/lib/sks/PTree/
cp /usr/share/doc/sks/sampleConfig/DB_CONFIG /var/lib/sks/DB/
/etc/init.d/sks start
I confess i'm doing this sort of blindly -- i don't know what
other consequences may result from this BDB config change.
Perhaps if this config change is necessary to avoid a hard hang, it
should be done during the postinst script?
Thanks for maintaining SKS in debian!
Regards,
--dkg
[0] http://lists.nongnu.org/archive/html/sks-devel/2012-06/msg00036.html
pgpQMOiF3UBFm.pgp
Description: PGP signature
