Discussion:
[Sks-devel] sks.daylightpirates.org is staying
Daniel Roesler
2018-07-19 18:17:15 UTC
Permalink
I'm staying, but I need some help.

My server (sks.daylightpirates.org) currently has an uptime of
97.95%, but every few hours the "sks db" process spikes to 100%
CPU which makes the web interface completely unresponsive, which
I'm guessing is why I keep getting kicked out of the pool.

In the db.log, for each of these events, there's the following
logs:
================
2018-07-19 18:04:30 add_keys_merge failed: Eventloop.SigAlarm
2018-07-19 18:04:38 Key addition failed: Eventloop.SigAlarm
================

After "Key addition failed", my server becomes responsive again.
I'm not having storage problems (/var/lib/sks is only 15GB,
probably due to DB_LOG_AUTOREMOVE being set), but the CPU spikes
are really annoying since it kicks me out of the pool.

Is there anything I can do to prevent these CPU spikes or
offload them to another process so the web interface stays up?


Thanks!
Daniel Roesler
***@gmail.com


For reference, here's my sksconfig:
================
# /var/lib/sks/sksconf
debuglevel: 3
hostname: sks.daylightpirates.org
nodename: server
hkp_address: 0.0.0.0
hkp_port: 11371
recon_port: 11370
server_contact: 0xE7F6FAD172EFEE3D
initial_stat:
disable_mailsync:
membership_reload_interval: 1
stat_hour: 12
max_matches: 500
================

And my KDB/DB_CONFIG:
================
set_flags DB_LOG_AUTOREMOVE
================
Daniel Roesler
2018-07-19 18:42:46 UTC
Permalink
Added an issue to the sks-keyserver bitbucket:

https://bitbucket.org/skskeyserver/sks-keyserver/issues/61/key-addition-failed-blocks-web-interface
Post by Daniel Roesler
I'm staying, but I need some help.
My server (sks.daylightpirates.org) currently has an uptime of
97.95%, but every few hours the "sks db" process spikes to 100%
CPU which makes the web interface completely unresponsive, which
I'm guessing is why I keep getting kicked out of the pool.
In the db.log, for each of these events, there's the following
================
2018-07-19 18:04:30 add_keys_merge failed: Eventloop.SigAlarm
2018-07-19 18:04:38 Key addition failed: Eventloop.SigAlarm
================
Gabor Kiss
2018-07-19 19:19:39 UTC
Permalink
Post by Daniel Roesler
My server (sks.daylightpirates.org) currently has an uptime of
97.95%, but every few hours the "sks db" process spikes to 100%
CPU which makes the web interface completely unresponsive, which
I'm guessing is why I keep getting kicked out of the pool.
In the db.log, for each of these events, there's the following
================
2018-07-19 18:04:30 add_keys_merge failed: Eventloop.SigAlarm
2018-07-19 18:04:38 Key addition failed: Eventloop.SigAlarm
================
After "Key addition failed", my server becomes responsive again.
I'm not having storage problems (/var/lib/sks is only 15GB,
probably due to DB_LOG_AUTOREMOVE being set), but the CPU spikes
are really annoying since it kicks me out of the pool.
The very same occurs at keys.niif.hu.

Gabor
Fabian A. Santiago
2018-07-19 19:35:28 UTC
Permalink
Post by Gabor Kiss
Post by Daniel Roesler
My server (sks.daylightpirates.org) currently has an uptime of
97.95%, but every few hours the "sks db" process spikes to 100%
CPU which makes the web interface completely unresponsive, which
I'm guessing is why I keep getting kicked out of the pool.
In the db.log, for each of these events, there's the following
================
2018-07-19 18:04:30 add_keys_merge failed: Eventloop.SigAlarm
2018-07-19 18:04:38 Key addition failed: Eventloop.SigAlarm
================
After "Key addition failed", my server becomes responsive again.
I'm not having storage problems (/var/lib/sks is only 15GB,
probably due to DB_LOG_AUTOREMOVE being set), but the CPU spikes
are really annoying since it kicks me out of the pool.
The very same occurs at keys.niif.hu.
Gabor
_______________________________________________
Sks-devel mailing list
https://lists.nongnu.org/mailman/listinfo/sks-devel
i actually experience this myself as well...constantly. Does Kristian F
maintain sks? has he commented on this before?
--
Fabian S.

OpenPGP:

0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key)

***

0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired, still valid)
Loading...