You may want to consider starting over once more after re-loading from a fresh key dump. Your server’s status page shows a total of 5,615,275, which is a delta of ~508,000 keys against the pool’s current mean. Having to process so many keys via the reconciliation process may put a strain on your peering partners. While many of the key dump sites have vanished, I believe you can get still pull a current one from some of the sources listed here: https://github.com/SKS-Keyserver/sks-keyserver/wiki/KeydumpSources#sources-of-keydumps
In particular, these look to be fully up to date:
On Apr 6, 2021, at 12:08, Andreas Puls <firstname.lastname@example.org
Am 06.04.2021 um 18:53 schrieb Robbert Müller:
On 2021-04-05 17:25, Andreas Puls wrote:
Am 05.04.2021 um 14:00 schrieb Robbert Müller:
On 2021-04-05 07:46, Kiss Gabor (Bitman) wrote:That was my first thought. I had the same issue with a non full dump
I've just noticed that key diff of ALL current 26 pool members is
Meanwhile keyserver.snt.utwente.nl is dropped from the pool
however it seems to be absolute healthy. Except its key diff: 73432.
I guess this this node got an attack-like burst of keys from outside.
(And this 73k extra keys distorted the average so much that everybody
seems to be lacking thousands of keys.)
During an OS upgrade i botched the postgresql database, and wiped
everything and loaded a keydump.
This was saturday.
Could, and if how, this result in having more keys they the rest of the
import and ran hockeypuck-pbuild twice.
But i think you killed your ptree too, right ? Maybe removing the ptree
and rebuilding could fix it.
Yeah, something was wrong here,
I wiped the ptree, and build it again with hockeypuck-pbuild, only now
i'm missing keys instead of having to many.
i've i'll see if the server will sync the keys back or that i have to
start over again.
The sync will work but need some time. Make sure that your peering
partner are working. Hockeypuck need some time to switch to another peer
if one is not working.