Andrey Korobkov <korob...@fryxell.ru> writes:
> That's good :)
> So, that was because SKS was listening on IPv4.
>
> But what about:
> 2011-04-07 00:57:02 Recon partner: <ADDR_INET
> [2001:a60:f01c:0:70:1:6:42]:11370>
> 2011-04-07 00:57:03 Initiating reconciliation
> 2011-04-07 00:57:05 <recon as client> error in callback.:
> Sys_error("Connection reset by peer")
>
> What does it mean?
Probably
2011-04-06 22:57:05 Reconciliation attempt from <ADDR_INET
[2001:470:1f15:16f0::1:1137]:35415> while gossip disabled. Ignoring.
Which I guess is happening when your server is contacting mine while
mine is currently getting updates from another server. You should
probably be able to get through next time (or maybe right now looking at
my logs)
Regards
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
pgp9SXbc3DdPz.pgp
Description: PGP signature
_______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
