:: [Libbitcoin] Fwd: Re: Large amount…
Etusivu
Poista viesti
Vastaa
Lähettäjä: Shawn Pringle
Päiväys:  
Vastaanottaja: libbitcoin
Aihe: [Libbitcoin] Fwd: Re: Large amount of failed connections
I think it is normal to have so many failed connections. A bitcoin core
client running behind some DHCP ISP, with a NAT router may keep the same IP
but the node wont be able to respond even if it is running.

This is the standard package that ISPs offer users.
---------- Forwarded message ----------
From: "Police Terror" <PoliceTerror@???>
Date: Jul 27, 2016 9:46 AM
Subject: Re: [Libbitcoin] Large amount of failed connections
To: <libbitcoin@???>
Cc:

ok, it was master branch btw.

Once resume sync is done, then things should be much better.

Eric Voskuil:
> Version?
>
> FYI the odds of a successful connection are about 1 in 5. This is why

version3 uses batch connection when generating connections from the pool.
>
> It is however possible that the pool can become starved of good

connections, as the connections are supplied by peers (not just at startup)
and there is no DoS protection. I have found that actual problems here are
rare and given other more significant necessary work I haven't prioritized
making the host pool more robust. The first step is to actually manage the
pool, aging connections out, requesting more when needed, falling back to
seed nodes at some point. I wouldn't restart to do this as it's very
disruptive and there's really no reason to do so.
>
> e
>
> -----Original Message-----
> From: Libbitcoin [mailto:libbitcoin-bounces@lists.dyne.org] On Behalf Of

Police Terror
> Sent: Wednesday, July 27, 2016 12:55 AM
> To: libbitcoin@???
> Subject: Re: [Libbitcoin] Large amount of failed connections
>
> Police Terror:
>> I notice there's no longer a hosts.cache file. Has it been disabled
>> because it was getting filled with bad hosts?
>
> This is wrong. Of course it was created when I stopped the node.
>
> However the node getting stuck cycling through hosts that don't work

makes initial sync difficult.
>
> Maybe there can be a piece of code whereby if there isn't a connection

after X attempts, then it will restart the bootstrap process and clear the
hosts cache. How does that sound?
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
>

_______________________________________________
Libbitcoin mailing list
Libbitcoin@???
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin