[Sks-devel] How to resolve this cycle of `add_keys_merge failed: Eventloop.SigAlarm` ?

[Paul M Furley]

Hi folks,

I've been following this bad key business since Friday when my server's 
disk filled up with logs and self destructed.

Since then I've:

- Rebuilt the server from a dump
- Added `set_flags DB_LOG_AUTOREMOVE` to /var/lib/sks/DB/DB_CONFIG
- Increased nginx's `client_max_body_size` from 8m to 32m 
(https://lists.nongnu.org/archive/html/sks-devel/2018-06/msg00016.html)
- Add monitoring to syslog for `SigAlarm` and nginx logs for timeout errors
- Restarted everything


... and I'm still in a cycle where something happens with recon that 
causes the server to become unresponsive, then ultimately logs the 
`Eventloop.SigAlarm` error into syslog. This is happening approximately 
9 times per hour.

During these periods any unfortunate client hitting my server in the 
pool gets a long wait followed by an nginx gateway timeout :(

I'm also seeing about 800Mb traffic each hour, more than the usual ~250Mb.

Here's a paste with the logs from two occurrences:

https://pad.riseup.net/p/vAJwQhL8uu69

Can anyone suggest a remedy?

Kind regards,

Paul

0xA999B7498D1A8DC473E53C92309F635DAD1B5517

signature.asc
Description: OpenPGP digital signature