tickets #26114
closedkeyserver.o.o - a love story
100%
Description
Hi all,
like in every good and trashy hollywood/bollywood love movie, two
individuums - in this case the keyserver and me - want to exchange their
data.
But of course - as always in those movies - a bad situation comes up,
the dad of the keyserver is against our data exchange and everything
ends up in a mess...
Maybe - the dad of the keyserver - reconsiders his choice and gives me
the possibility to upload keys and sync the keyserver with the outside
world again, as I try to work with the keyserver every day, I promise to
always upload there an updated key of myself and really promise to be a
valuable part of the GPG community signing only keys where I checked a
passport and swear on the book of "Honest Ahmed Used Cars and
Certificates - Keysigning howto" before. Furthermore, I will consider
everybody to sign keys, as it makes the community more valuable.
So please dad of keyserver.o.o - give yourself a small kick - and bring
this nice service back2life - which means - let it sync with the outside
world - pool it with sks - and let the GPG pubkeys have many many
beautiful copies out there in the world which will make the family
bigger :).
Best regards,
a sad user
--
Thorsten
Updated by cboltz over 6 years ago
- Assignee set to Anonymous
- Private changed from Yes to No
Updated by Anonymous over 6 years ago
- Category set to Servers hosted in NBG
- % Done changed from 0 to 30
The filesystem was damaged in a way I was unable to recover: normal files still existed and where (mostly) readable, but the database reported corruption and unrecoverable damages. I tried what I can to help the database system to recover - but in the end I have to admit that all ~4 million key entries are lost.
Currently trying to get a dump somewhere...
Updated by Anonymous over 6 years ago
- Status changed from In Progress to Closed
- % Done changed from 30 to 100
Re-setup the whole database. We are currently 2268 keys behind, but syncing.
Need to find a way how to integrate and sync our new backup keyserver (running in Provo) now - but the initial issue should be fixed now.