Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wp4BT-00081o-56 for bitcoin-development@lists.sourceforge.net; Mon, 26 May 2014 23:19:59 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of m.gmane.org designates 80.91.229.3 as permitted sender) client-ip=80.91.229.3; envelope-from=gcbd-bitcoin-development@m.gmane.org; helo=plane.gmane.org; Received: from plane.gmane.org ([80.91.229.3]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Wp4BR-0001xf-SM for bitcoin-development@lists.sourceforge.net; Mon, 26 May 2014 23:19:59 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Wp4BK-0007t3-Vj for bitcoin-development@lists.sourceforge.net; Tue, 27 May 2014 01:19:50 +0200 Received: from f053012018.adsl.alicedsl.de ([78.53.12.18]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 27 May 2014 01:19:50 +0200 Received: from andreas by f053012018.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 27 May 2014 01:19:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Andreas Schildbach Date: Tue, 27 May 2014 01:19:39 +0200 Message-ID: References: <20140523221726.GA30143@petertodd.org> <20140526163753.GA18693@petertodd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: f053012018.adsl.alicedsl.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 In-Reply-To: X-Enigmail-Version: 1.5.2 X-Spam-Score: -1.1 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.91.229.3 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 1.1 DKIM_ADSP_ALL No valid author signature, domain signs all mail -0.0 SPF_PASS SPF: sender matches SPF record -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Wp4BR-0001xf-SM Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2014 23:19:59 -0000 On 05/27/2014 12:39 AM, Peter Todd wrote: > On 27 May 2014 01:12:05 GMT+03:00, Andreas Schildbach > 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?