Hi,

@Gabor

all right, I have deleted all entries with connection errors:

2013-12-29 13:47:35 <recon as client> error in callback.: Unix error: 
Connection refused - connect()
2013-12-29 13:48:36 Recon partner: <ADDR_INET [31.xxx.xxx.xxx]:11370>
2013-12-29 13:48:36 Initiating reconciliation
2013-12-29 14:06:57 <recon as client> error in callback.: Sys_error("Connection 
reset by peer")
2013-12-29 14:07:58 Recon partner: <ADDR_INET [62.xxx.xxx.xxx]:11370>
2013-12-29 14:07:58 Initiating reconciliation
2013-12-29 14:08:43 <recon as client> callback timed out.

well, i’m waiting for permission to activate the individual server …

@Andreas

thanks, der SKS in der FreeBSD Jail is happy :D

best regards,
Daniel

> Ich habe deine beiden Server hinzugefügt, wäre nett wenn Du meine Zeile
> in die membership eintragen würdest
> 
>> Thank you,
>> Daniel Plominski
> Gruss und guten Rutsch
>  Andreas


Am 29.12.2013 um 07:58 schrieb Gabor Kiss <[email protected]>:

>> I am looking for peers for a new SKS keyserver installation.
>> 
>> I am running SKS version 1.1.4, on keyserver.plitc.eu.
>> {We are an ISP with public services}.
>> The server is physically located in Germany (EU).
>> The machine has IPv6 connectivity.
> 
> Dear Daniel,
> 
> Your status page says your server allegedly has 35 peers (including itself).
> I guess most of these operators did not allowed you to configure
> their servers into you membership file. (Actually I checked three.)
> Getting gossip partner does not work this way. :-(
> You must wait for the permissions.
> 
> Regards
> 
> Gabor

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
Sks-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/sks-devel

Reply via email to