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; 
To: bitcoin-development@lists.sourceforge.net
From: Andreas Schildbach <andreas@schildbach.de>
Date: Tue, 27 May 2014 01:19:39 +0200
Message-ID: <lm0i6b$4m9$1@ger.gmane.org>
References: <20140523221726.GA30143@petertodd.org>
	<lltfaa$2lv$1@ger.gmane.org>	<20140526163753.GA18693@petertodd.org>
	<lm0e7m$thg$1@ger.gmane.org>
	<b6884e2a-42b7-4c3f-a034-3a466aeec751@email.android.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.5.0
In-Reply-To: <b6884e2a-42b7-4c3f-a034-3a466aeec751@email.android.com>
Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up
	again
Precedence: list

On 05/27/2014 12:39 AM, Peter Todd wrote:

> On 27 May 2014 01:12:05 GMT+03:00, Andreas Schildbach
> <andreas@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?