📅 Original date posted:2014-05-26
📝 Original message:On 05/27/2014 12:39 AM, Peter Todd wrote:
> On 27 May 2014 01:12:05 GMT+03:00, Andreas Schildbach
> <andreas at 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?
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 15:21:59
in reply to nevent1q…mp9z
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Published at
2023-06-07 15:21:59Event JSON
{
"id": "e8f73cf89d8f9ef9c7e01a652010a59208fe0198fca15f4f36b213a8bc162a64",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686151319,
"kind": 1,
"tags": [
[
"e",
"1df32530851d221cbbd33f32f81f5456a402725593653d36a2348e31d3f14708",
"",
"root"
],
[
"e",
"d895583f29cf7c81d4654615eb31181726eb17379624ee79a85da29678b5b8ff",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2014-05-26\n📝 Original message:On 05/27/2014 12:39 AM, Peter Todd wrote:\n\n\u003e On 27 May 2014 01:12:05 GMT+03:00, Andreas Schildbach\n\u003e \u003candreas at schildbach.de\u003e wrote:\n\u003e\u003e You're very quick to point at others. Especially since they run \n\u003e\u003e software that had the time to mature for about 30 years, and the\n\u003e\u003e protocol didn't really change since then...\n\u003e \n\u003e\u003e The last time it didn't work, the bug -- non RFC-conformance --\n\u003e\u003e was on the bitcoin seeders side. ISPs do weird things with DNS,\n\u003e\u003e but usually they stay within the RFC.\n\u003e \n\u003e\u003e Anyway, without logs we don't have a chance to debug this issue.\n\u003e\u003e Any chance you could add simple logging to the seeder?\n\u003e \n\u003e\u003e DNS via HTTP? Never heard of that, at least it sounds weird as\n\u003e\u003e well.\n\u003e \n\u003e Hey, really sorry I don't have the time to fix this issue, been\n\u003e travelling for a few weeks for my consulting job. If you want to\n\u003e step up and volunteer please feel free.\n\nI'm already volunteering. At least I don't get paid for my efforts in\ndebugging the seed infrastructure.\n\nCan you verify if your copy of the seeder contains the commit\n8dcc006e6256cb746c2b025daf3df41baa26353e ?\n\nIt fixed a bug that has exactly the symptoms we currently see.\n\nI wonder if the restart of your server actually changed/fixed\nanything. If you got a SERVFAIL this may be because you were traveling\nthrough parts of the world that can't reach your server. Did you\nactually try at home, before the restart?",
"sig": "969caccc339a0cd171a50b7aab6429289884e00a93bfb4e931a8369cb3ee1efba3ae8df7828c801b7975d0cd367215621cfe6cc2996aafe12430e28ef66a6ff6"
}