Hi,
I can open a PR and let Casey Marshall decide if it's bringing any
long-term value for Hockeypuck. I'm somehow not convinced it is the case
because the patch is trying to only fulfill a contract with SKS status
page generator
<https://git.sumptuouscapital.com/?p=sks-keyservers-pool.git;a=summary>.
And the patch alone is not enough to satisfy the logic from
sks-keyservers.net/status-srv/sks_get_peer_data.php
<https://git.sumptuouscapital.com/?p=sks-keyservers-pool.git;a=blob;f=sks-keyservers.net/status-srv/sks_get_peer_data.php;h=411d2aa0145b511ccccf7fa3197d3e33e9391466;hb=668504fbc685cf84ebc822fea71388b4999edd68>
I had to play with mod_rewrite and force a redirect from
//pks/lookup?op=stats&options=mr/ to //pks/lookup?op=stats /to let the
script parse HTML. I don't have a proper explanation why peers and recon
port are not picked from the produced JSON but left out (line 286/287).
Regards,
Martin
On 21/03/2021 18:45, Ryan Hunt wrote:
This is great, thank you for the effort you put into this. I pulled my
keyserver out long ago and am building two news ones now that Hockeypuck
finally looks ready to replace SKS
Are you going to try to merge this back upstream eventually?
-Ryan
On Mar 21, 2021, at 12:38 PM, Martin Dobrev <mar...@dobrev.eu> wrote:
Thanks everyone that messaged me privately. I recon many others are wondering
how my cluster is being setup, so I prepared a small repository with sample
configuration available here:
https://github.com/mclueppers/sks-keyserver-clustering
I hope it helps.
On 21/03/2021 00:38, Martin Dobrev wrote:
Good afternoon,
I've spent last few weeks fiddling and trying to revive three of the SKS nodes
from my cluster. It takes recently more time recovering from dumps than
actually running the service so I decided to give Hockeypuck a proper go this
time.
New cluster is dual node, running Hockeypuck 2.1.0 + some changes to pass SKS
keyservers status checks available here:
https://github.com/mclueppers/hockeypuck/tree/sks-compatability
Regards,
Martin
