sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] Running a non-pool keyserver & identifying offline peers


From: Kristian Fiskerstrand
Subject: Re: [Sks-devel] Running a non-pool keyserver & identifying offline peers
Date: Fri, 01 Aug 2014 12:27:45 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 08/01/2014 12:08 PM, Pete Stephenson wrote:
> Dear all,
> 

...

> 
> Is there a way to have the public and private systems stay in sync,
> but privately?

One option is using a local hostname in the peer file and put an entry
in /etc/hosts for it. Another is that I can put it in the global
exclude list of the pool.

> 
> 2. I have recently observed lines such as the following appearing
> in my recon.log:
> 
> 2014-08-01 07:21:36 <recon as client> error in callback.: 
> Sys_error("Connection reset by peer") 2014-08-01 07:23:38 <recon as
> client> error in callback.: Unix error: Connection refused -
> connect()
> 
> I assume this means that a remote keyserver peer is offline or
> otherwise not responding to recon attempts. However, the recon log
> does not indicate which peer is not responding, which makes
> diagnosing the issue a bit difficult.
> 
> Is there a way of determining which peer(s) are having issues?

This message also shows up if gossip is temporarily disabled due to
the server currently being in a recon process with another server, so
nothing needs to be wrong per se.

- -- 
- ----------------------------
Kristian Fiskerstrand
Blog: http://blog.sumptuouscapital.com
Twitter: @krifisk
- ----------------------------
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
- ----------------------------
"Be a yardstick of quality. Some people aren't used to an environment
where excellence is expected."
(Steve Jobs)
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJT22ugAAoJEPw7F94F4TagBOoP/16QrI5zZpG/FZSs8ZaVFw9G
DcMPn0ESaR6YWorLvitdjXwV6ivUSrTdtIdOBavvROT9VAqLdJsbfo6kjttxTe2Z
4mkI6DTw1E4nZlQopdTO6Yo59oBxEn80+V89Q87M4J1WCVEPxKfTOE+TDwIxJCot
M6MownN9fIFYP6DJQ62wsFJary7tK6KW6Rtgh6ELYUyhr0l2y/oKkWWAaxtnopwa
GvqveF9xiqoPhc0R70uvNBY6aT8wzUHdzaFAOczIJPZ3pVCupcBOk3DQMNPLVo6e
2+ue+xDGUulPXYJXERWx4XjMgi5x4V0JDKjGs5g8aHC2PlR+ECrLIZRzLc2xhd57
R7NFdRRQJW4pqkt/VIe3pt7a40S43tsEdxbyXbwTbV3d0jpZ5/6U+rwn8sjR8zii
7uGiN5xtxrcetHbPH84zzoZpFZ/EYEgcP+XZMPWW8IFbyIc1wJkrgTBJvfvGL+td
eoSDJmiBa6D2zCYQYWLuRj47U1fKCxNwrCgrzdOq5Eho2hvNso2J5b34W76YiA5+
K1OvGxPYsdbKD3Mje8b1+6QX1vypQcxoW8g4egatsf6XKV8+mYrWjpW46DhlrAGh
r48eXrVKk65jO6+Lp8Wn9QLI9LTqmZPQGbUSnSm2bRRXzRs8sXTqpEQGV2IiMpP1
KD4DOZZCtYbEyQz99Iuy
=cklf
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]