1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ayeowch@gmail.com>) id 1WSuAB-00048S-CE
for bitcoin-development@lists.sourceforge.net;
Wed, 26 Mar 2014 20:11:03 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.175 as permitted sender)
client-ip=209.85.192.175; envelope-from=ayeowch@gmail.com;
helo=mail-pd0-f175.google.com;
Received: from mail-pd0-f175.google.com ([209.85.192.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WSuAA-0005qN-9D
for bitcoin-development@lists.sourceforge.net;
Wed, 26 Mar 2014 20:11:03 +0000
Received: by mail-pd0-f175.google.com with SMTP id x10so2342131pdj.20
for <bitcoin-development@lists.sourceforge.net>;
Wed, 26 Mar 2014 13:10:56 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.68.139.137 with SMTP id qy9mr87624496pbb.11.1395864656420;
Wed, 26 Mar 2014 13:10:56 -0700 (PDT)
Received: by 10.69.8.66 with HTTP; Wed, 26 Mar 2014 13:10:56 -0700 (PDT)
In-Reply-To: <CANEZrP2HuZc_5E0o5T6DUOvmFr8qmYrhPC9S-VAhJWmA=CbtDA@mail.gmail.com>
References: <CANEZrP2HuZc_5E0o5T6DUOvmFr8qmYrhPC9S-VAhJWmA=CbtDA@mail.gmail.com>
Date: Thu, 27 Mar 2014 07:10:56 +1100
Message-ID: <CAA3bHnzvOj7yjgLJ_fsZN1f1Mjp+QTE_=iaC=O_V1KTii79Y3w@mail.gmail.com>
From: Addy Yeow <ayeowch@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=001a11c3c1e400272c04f588113b
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [209.85.192.175 listed in list.dnswl.org]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(ayeowch[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WSuAA-0005qN-9D
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Sudden temporary drop in reachable nodes?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 26 Mar 2014 20:11:03 -0000
--001a11c3c1e400272c04f588113b
Content-Type: text/plain; charset=ISO-8859-1
Hi Mike,
That was because I had to restart the crawler for update. This disconnects
the crawler from all reachable nodes temporarily and it will take about 15
minutes (3 snapshots) before the crawler stabilize again. I will look into
annotating these drops with a note.
Cheers,
Addy
On Thu, Mar 27, 2014 at 12:07 AM, Mike Hearn <mike@plan99.net> wrote:
> Hey Addy,
>
> I am seeing a big drop in reachable nodes on
> http://getaddr.bitnodes.io/dashboard/ starting from about March 25th
> 7:20pm and coming back 9:35pm. Is this a glitch in the monitoring system or
> did some real network event happen then?
>
--001a11c3c1e400272c04f588113b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi Mike,<div><br></div><div>That was because I had to rest=
art the crawler for update. This disconnects the crawler from all reachable=
nodes temporarily and it will take about 15 minutes (3 snapshots) before t=
he crawler stabilize again. I will look into annotating these drops with a =
note.</div>
<div><br></div><div>Cheers,</div><div>Addy</div></div><div class=3D"gmail_e=
xtra"><br><br><div class=3D"gmail_quote">On Thu, Mar 27, 2014 at 12:07 AM, =
Mike Hearn <span dir=3D"ltr"><<a href=3D"mailto:mike@plan99.net" target=
=3D"_blank">mike@plan99.net</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hey Addy,<div><br></div><di=
v>I am seeing a big drop in reachable nodes on=A0<a href=3D"http://getaddr.=
bitnodes.io/dashboard/" target=3D"_blank">http://getaddr.bitnodes.io/dashbo=
ard/</a> starting from about March 25th 7:20pm and coming back 9:35pm. Is t=
his a glitch in the monitoring system or did some real network event happen=
then?</div>
</div>
</blockquote></div><br></div>
--001a11c3c1e400272c04f588113b--
|
