ok so now im thoroughly stumped, built a couple versions and all but the debian combo cores.
sks-1.1.2 - bdb 5.2 - CORE sks-1.1.2 - bdb 4.7 - CORE sks-1.1.1 - bdb 5.2 - CORE sks-1.1.1 - bdb 4.7 - Fine (basically same as debian package) I'll keep on digging, both my servers are showing same behavior.. Pretty standard Debian Squeeze (w/3.0.4 Kernel) inside KVM.. downloaded source from oracle's site for BDB, built and installed w/default options.. Must be something environmental, sigh. I am going to revert sks2.webtru.st back to the debian package and setup another KVM for further investigation.. im thinking its my Kernel or something PVE related. on another note, I was getting constant PTree corruption using the kvm-clock.. i switched to the acpi_pm clock after being pointed to a previous issue with Xen and its default clock; things seem better but its too early yet to see if its a perm solution (over 24h thus far w/out corruption vs 4h tops before) -Ryan On Oct 12, 2011, at 6:50 PM, John Marshall wrote: > On Wed, 12 Oct 2011, 15:52 -0600, Ryan wrote: >> Debian Squeeze, built and installed bdb-5.2 and trying to build database >> from dump: > > BDB 5.2.36 or an earlier (e.g. BDB 5.2.28) release? I had problems with > 5.2.28 (different to yours) which were resolved after rebuilding with > 5.2.36. I haven't tried building a key database. > > -- > John Marshall > _______________________________________________ > Sks-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/sks-devel
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Sks-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/sks-devel
