Re: [Bitcoin-development] Cut-through propagation of blocks
it: I'd be much more likely to run an experimental gateway in another process on a node than experimental p2p code inside my production bitcoinds themselves. Yes, it's certainly better to do that during the development phase. However if it does turn out to be good and valuable then it'd eventually need to be integrated or rewritten into Core anyway, lest we accidentally increase the setup cost of running a node and end up with a two-tier network. And if the code will eventually want to be merged into Core anyway, it might as well be implemented into it directly, perhaps behind a switch that can disable those codepaths if something goes wrong. So I think the tradeoffs here are rather complicated and subtle. -- The best possible search technologies are now affordable for all companies. Download your FREE open source Enterprise Search Engine today! Our experts will assist you in its installation for $59/mo, no commitment. Test it for FREE on our Cloud platform anytime! http://pubads.g.doubleclick.net/gampad/clk?id=145328191iu=/4140/ostg.clktrk___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
On Sun, May 25, 2014 at 09:12:10PM +0200, Andreas Schildbach wrote: Thanks for looking at the issue. Unfortunately, it still fails for me: $ nslookup testnet-seed.bitcoin.petertodd.org Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find testnet-seed.bitcoin.petertodd.org: SERVFAIL Like I said, can you look at the logfiles how the requests arrive? There are no logfiles for DNS requests. I just checked on EC2 and my cellphone internet connection here in Tel Aviv; both work fine. My best guess is that your DNS resolver locally or at your ISP is unable to deal with the fact that the second DNS seed serving the domain testnet-seed.bitcoin.petertodd.org happens to be down right now. Note that some ISP's appear to both run buggy DNS servers, and redirect traffic meant to go to Google's 8.8.8 and 8.8.4.4 DNS servers to their own servers. I'd suggest that someone setup an alternate HTTP(S) based DNS seed for protocol redundency. What particular thing did you fix? It would be good to know for future outages. Dunno exactly. It appeared to be running fine when I logged into the machine, but for whatever reason DNS requests just weren't getting resolved. Restarted and it was ok again. -- 'peter'[:-1]@petertodd.org signature.asc Description: Digital signature -- The best possible search technologies are now affordable for all companies. Download your FREE open source Enterprise Search Engine today! Our experts will assist you in its installation for $59/mo, no commitment. Test it for FREE on our Cloud platform anytime! http://pubads.g.doubleclick.net/gampad/clk?id=145328191iu=/4140/ostg.clktrk___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
You're very quick to point at others. Especially since they run software that had the time to mature for about 30 years, and the protocol didn't really change since then... The last time it didn't work, the bug -- non RFC-conformance -- was on the bitcoin seeders side. ISPs do weird things with DNS, but usually they stay within the RFC. Anyway, without logs we don't have a chance to debug this issue. Any chance you could add simple logging to the seeder? DNS via HTTP? Never heard of that, at least it sounds weird as well. On 05/26/2014 06:37 PM, Peter Todd wrote: On Sun, May 25, 2014 at 09:12:10PM +0200, Andreas Schildbach wrote: Thanks for looking at the issue. Unfortunately, it still fails for me: $ nslookup testnet-seed.bitcoin.petertodd.org Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find testnet-seed.bitcoin.petertodd.org: SERVFAIL Like I said, can you look at the logfiles how the requests arrive? There are no logfiles for DNS requests. I just checked on EC2 and my cellphone internet connection here in Tel Aviv; both work fine. My best guess is that your DNS resolver locally or at your ISP is unable to deal with the fact that the second DNS seed serving the domain testnet-seed.bitcoin.petertodd.org happens to be down right now. Note that some ISP's appear to both run buggy DNS servers, and redirect traffic meant to go to Google's 8.8.8 and 8.8.4.4 DNS servers to their own servers. I'd suggest that someone setup an alternate HTTP(S) based DNS seed for protocol redundency. What particular thing did you fix? It would be good to know for future outages. Dunno exactly. It appeared to be running fine when I logged into the machine, but for whatever reason DNS requests just weren't getting resolved. Restarted and it was ok again. -- The best possible search technologies are now affordable for all companies. Download your FREE open source Enterprise Search Engine today! Our experts will assist you in its installation for $59/mo, no commitment. Test it for FREE on our Cloud platform anytime! http://pubads.g.doubleclick.net/gampad/clk?id=145328191iu=/4140/ostg.clktrk ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- The best possible search technologies are now affordable for all companies. Download your FREE open source Enterprise Search Engine today! Our experts will assist you in its installation for $59/mo, no commitment. Test it for FREE on our Cloud platform anytime! http://pubads.g.doubleclick.net/gampad/clk?id=145328191iu=/4140/ostg.clktrk ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
On 05/27/2014 12:39 AM, Peter Todd wrote: On 27 May 2014 01:12:05 GMT+03:00, Andreas Schildbach andr...@schildbach.de wrote: You're very quick to point at others. Especially since they run software that had the time to mature for about 30 years, and the protocol didn't really change since then... The last time it didn't work, the bug -- non RFC-conformance -- was on the bitcoin seeders side. ISPs do weird things with DNS, but usually they stay within the RFC. Anyway, without logs we don't have a chance to debug this issue. Any chance you could add simple logging to the seeder? DNS via HTTP? Never heard of that, at least it sounds weird as well. Hey, really sorry I don't have the time to fix this issue, been travelling for a few weeks for my consulting job. If you want to step up and volunteer please feel free. I'm already volunteering. At least I don't get paid for my efforts in debugging the seed infrastructure. Can you verify if your copy of the seeder contains the commit 8dcc006e6256cb746c2b025daf3df41baa26353e ? It fixed a bug that has exactly the symptoms we currently see. I wonder if the restart of your server actually changed/fixed anything. If you got a SERVFAIL this may be because you were traveling through parts of the world that can't reach your server. Did you actually try at home, before the restart? -- The best possible search technologies are now affordable for all companies. Download your FREE open source Enterprise Search Engine today! Our experts will assist you in its installation for $59/mo, no commitment. Test it for FREE on our Cloud platform anytime! http://pubads.g.doubleclick.net/gampad/clk?id=145328191iu=/4140/ostg.clktrk ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development