I've setup my cluster with separate filesystems, as I believe locks are
created on the bdb so the sks instances would lock each other if they
shared, otherwise i would have used nfs or gluster.
Kind Regards,
Mike
On 24/08/18 10:36, Gabor Kiss wrote:
> On Thu, 23 Aug 2018, Kristian Fiskerstrand
On 26/07/18 15:41, Shengjing Zhu wrote:
> On Thu, Jul 26, 2018 at 10:17 PM Matthias Wassermann
> wrote:
>> I have loaded a keydump from ftp://keyserver.mattrude.com/current,
>> dated 2018-07-23.
>> I see 5102357 keys loaded.
> It's far behind the network, currently it's near 5244773.
>
23rd was
I suspect the injection of keys triggers the berkley db auto-clean job,
which wipes out the daily historic data (maybe).
On 23/07/18 17:36, Michael Jones wrote:
>
> also, i can see there seems to be alot more keys the last 2 days;
>
> key count
> On 23/07/18 17:33, Michael Jones w
also, i can see there seems to be alot more keys the last 2 days;
key count
On 23/07/18 17:33, Michael Jones wrote:
>
> Why do all of the sks keyservers that are in sync have only a history
> of 2 days?
>
> in sync
>
>
> vs:
>
> out of sync
_
Why do all of the sks keyservers that are in sync have only a history of
2 days?
in sync
vs:
out of sync
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel
Hi,
I was away on work, came back to one of nodes I host ran out of disk space.
Users of the service would not have been effected as this node doesn't
serve web traffic other than the default key stats page.
And keys would have continued to sync via a backup node.
Node is back in and fixed.
some nodes have the db cleanup, some nodes have loggging;
Graph of disk space
There was definitely an injection of keys, will perform some clean up
ops later.
Kind Regards,
Mike
On 15/06/18 13:27, Paul M Furley wrote:
> Glad I wasn't the only one :) keyserver.paulfurley.com also got
>
What if the approach was to either have a web of trust to whitelist users
able to upload images, or even more stringent strip all image data.
Is image data essential to operating?
I hardly ever look at the images, and these images could be shared via
other means.
The keyservers would continue
Time for an upgrade of disk space on my nodes, if anyone is interested
in the usage over time, here's a 6month graph;
zabbix, disk usage
signature.asc
Description: OpenPGP digital signature
___
Sks-devel mailing list
Sks-devel@nongnu.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/11/16 15:20, Valentin Sundermann wrote:
> Hey,
>
There seems to be some HSTS setup blocking access to
http://keys.vsund.de:11371/pks/lookup?op=stats ?
>>> Not HSTS but;
> HSTS only prevents a "real" browser from viewing it. As of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/11/16 04:16, Michael Jones wrote:
> On 18/11/16 23:55, Kristian Fiskerstrand wrote:
>> On 11/19/2016 12:43 AM, Valentin Sundermann wrote:
>>>> Hi,
>>>>>> Do you mind me asking how you got those charts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/11/16 23:55, Kristian Fiskerstrand wrote:
> On 11/19/2016 12:43 AM, Valentin Sundermann wrote:
>>> Hi,
> Do you mind me asking how you got those charts on your
> page? Tried the Github files linked to at the bottom but
> they only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/10/16 21:44, Valentin Sundermann wrote:
>> However, my key server,
>>> keyserver.brian.minton.name, does not appear in the pool status
>>> page. Not even in the "Servers currently not in the pool"
>>> section. I thought it would automatically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I run sks.mj2.uk.
I've introduced a few things in haproxy including master node auto
failover (failover master node will recon with the master node until
the master node falls down, then the failover node will recon with
normal peers).
I need
On 14/09/16 15:27, Valentin Sundermann wrote:
> Hey sks-devel,
>
> when searching for common terms (i.e. "test") on a keyserver, I
> hit a limit of matches sometimes.
>
> Assumed that I'd be a bad person, I should be able to make a
> choosen key unusable by creating and uploading keys with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Introduced my first 1.1.6 node.
CentOS7
Hostname: sks.mj2.uk
Nodename: node3.sks.mj2.uk
Version:1.1.6
Will review in a few days.
Kind Regards,
Mike
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/08/16 15:09, Danny Horne wrote:
> If you mean the dump I checked on both occasions and all was well.
> Going to strip everything out and use /var/whatever as the base
> directory (every howto I've seen says use that directory), just
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
anyone willing to peer in Eu (Server in france).
Kind Regards,
Mike
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBCAAGBQJWQUiRAAoJEOYwtpHNe8FmY38H/R0u+zAwnefNi9OsjJE2JEnp
18 matches
Mail list logo
