due to the poor quality of sks software and the problems continuing with sks keyserver, I decided to setup a systemd-timer for now that restarts sks-db and sks-recon hourly on keyserver1.infra.o.o just to keep you informed. This is a hack, not a solution :( Best regards, Thorsten Am 04.12.18 um 20:09 schrieb admin@opensuse.org:
[openSUSE Tracker] Issue #44726 has been updated by TBro.
Status changed from New to Resolved Assignee set to TBro % Done changed from 0 to 100
Unfortunately there is a wave of "attacks" going on sks-keyserver network and it shuts down the database from time to time.
To mitigate that I added the following to the service files now - by hand - to keep at least the service up and running on failure.
Restart=on-failure RestartSec=3s
Best regards, Thorsten
---------------------------------------- tickets #44726: keyserver https://progress.opensuse.org/issues/44726#change-171332
* Author: zbalogh@suse.de * Status: Resolved * Priority: Normal * Assignee: TBro * Category: * Target version: ---------------------------------------- Hello,
I am doing onboarding for newcomers and all of them needs to have properly signed PGP keys.
During the last few weeks (months) the keyserver.opensuse.org is very often out of service.
cheers,
Zoltan
---Files-------------------------------- pEpkey.asc (1.72 KB)
-- Thorsten Bro <Thorsten.Bro@suse.com> - PES -> Engineering Services -> SUSE IT - SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org