sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Sks-devel] Raising Sys.Break -- PTree may be corrupted: Failure("add_to


From: Christoph Anton Mitterer
Subject: [Sks-devel] Raising Sys.Break -- PTree may be corrupted: Failure("add_to_node: attempt to reinsert element into prefix tree")
Date: Wed, 31 Jul 2013 15:48:14 +0200

Hi.

As mentioned previously I'm in the process of migrating/re-installing my
SKS instance at much better machine...

I run SKS 1.1.3 from Debian sid (which has BDB 5.1, IIRC).

Just for trying, I dumped the keydb from my old server, and made a full
build on the new one (which worked fine, i.e. no errors[0] during that
were shown).

Anyway, when I now start sks, then the db process seems to run fine:
2013-07-31 05:16:11 Opening KeyDB database
2013-07-31 05:16:11 Calculating DB stats
2013-07-31 05:16:15 Done calculating DB stats
2013-07-31 05:16:15 Database opened
2013-07-31 05:16:15 Applied filters: yminsky.dedup, yminsky.merge
2013-07-31 05:16:15 Sending LogResp size 62
2013-07-31 06:16:15 Checkpointing database
2013-07-31 06:16:15 Checkpointing complete
2013-07-31 07:16:15 Checkpointing database
2013-07-31 07:16:15 Checkpointing complete


But the recon process just dies a few seconds after it started:
2013-07-31 05:16:11 sks_recon, SKS version 1.1.3
2013-07-31 05:16:11 Copyright Yaron Minsky 2002-2003
2013-07-31 05:16:11 Licensed under GPL.  See COPYING file for details
2013-07-31 05:16:11 Opening PTree database
2013-07-31 05:16:11 Setting up PTree data structure
2013-07-31 05:16:11 PTree setup complete
2013-07-31 05:16:15 Raising Sys.Break -- PTree may be corrupted:
Failure("add_to_node: attempt to reinsert element into prefix tree")
2013-07-31 05:16:15 DB closed

(again, this is a fresh install).


sks cleandb didn't help.


I looked around in the archive and past reports mentioned problems on
VMs,... well the OLD sks instance (i.e. the one I made the keydump on)
was a VM,.. but the new node is actually a physical node.


My sksconf is rather boring: 
hostname: a.keyserver.pki.scientia.net
hkp_address: localhost
membership_reload_interval: 1
recon_address: someIP
disable_mailsync: 
from_addr: "scientia.net OpenPGP Keyservers - Mail Gateway <address@hidden>"
initial_stat: 

The membership file was still empty, as I just wanted to run it for a
test.


Cheers,
Chris.


[0] Though I've originally had the problems mentioned here:
https://bitbucket.org/skskeyserver/sks-keyserver/issue/8

Attachment: smime.p7s
Description: S/MIME cryptographic signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]