Fwd: Probe 2317 (home fibre) is disconnected
strange, connectivity seems fine to me at least within BT network range and HSO network range ? Should I reset the probe or this is a bigger monitoring probe failure ? Colin Begin forwarded message:
From: RIPE Atlas <atlas@ripe.net> Subject: Probe 2317 (home fibre) is disconnected Date: 29 July 2014 12:30:05 BST To: colin johnston <colinj@mx5.org.uk> Delivered-To: colinj@mx5.org.uk Received: by 10.70.41.145 with SMTP id f17csp332256pdl; Tue, 29 Jul 2014 04:30:32 -0700 (PDT) Received: from koko.ripe.net (koko.ripe.net. [2001:67c:2e8:11::c100:1348]) by mx.google.com with ESMTPS id f10si19194016wic.74.2014.07.29.04.30.19 for <colinj@mx5.org.uk> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Jul 2014 04:30:20 -0700 (PDT) Received: from janus.atlas.ripe.net ([193.0.19.13]) by koko.ripe.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <atlas@ripe.net>) id 1XC5bZ-0004TU-Nf for colinj@mx5.org.uk; Tue, 29 Jul 2014 13:30:08 +0200 Received: from localhost.localdomain ([127.0.0.1] helo=janus.atlas.ripe.net) by janus.atlas.ripe.net with esmtp (Exim 4.72) (envelope-from <atlas@ripe.net>) id 1XC5bZ-00004y-IA for colinj@mx5.org.uk; Tue, 29 Jul 2014 11:30:05 +0000 X-Received: by 10.180.75.230 with SMTP id f6mr41435469wiw.5.1406633431897; Tue, 29 Jul 2014 04:30:31 -0700 (PDT) Return-Path: <atlas@ripe.net> Received-Spf: none (google.com: atlas@ripe.net does not designate permitted sender hosts) client-ip=2001:67c:2e8:11::c100:1348; Authentication-Results: mx.google.com; spf=neutral (google.com: atlas@ripe.net does not designate permitted sender hosts) smtp.mail=atlas@ripe.net Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Message-Id: <20140729113005.32636.40047@janus.atlas.ripe.net> X-Ripe-Spam-Level: / X-Ripe-Spam-Report: Spam Total Points: 0.4 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 4.0 DCC_CHECK Detected as bulk mail by DCC (dcc-servers.net) X-Ripe-Signature: 407c82a9d3629e01ca957e4b84b7f67191521e4a20cb459dafae86d3fab252b9
Dear colin,
Your probe 2317 has been disconnected since 2014-07-29 10:38:01 UTC.
This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes.
If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/2317/, and click the "edit" button under "Notifications".
Kind regards,
RIPE Atlas Team
I have this over and over, too. The probes seem to be unstable and need at least half an hour to re-register after the IP address has changed. Meanwhile I just ignore it ... Am 2014-07-29 13:34, schrieb Colin Johnston:
strange, connectivity seems fine to me at least within BT network range and HSO network range ?
Should I reset the probe or this is a bigger monitoring probe failure ?
Colin
Begin forwarded message:
FROM: RIPE Atlas <atlas@ripe.net>
SUBJECT: PROBE 2317 (HOME FIBRE) IS DISCONNECTED
DATE: 29 July 2014 12:30:05 BST
TO: colin johnston <colinj@mx5.org.uk>
DELIVERED-TO: colinj@mx5.org.uk
RECEIVED: by 10.70.41.145 with SMTP id f17csp332256pdl; Tue, 29 Jul 2014 04:30:32 -0700 (PDT)
RECEIVED: from koko.ripe.net [1] (koko.ripe.net [1]. [2001:67c:2e8:11::c100:1348]) by mx.google.com [2] with ESMTPS id f10si19194016wic.74.2014.07.29.04.30.19 for <colinj@mx5.org.uk> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Jul 2014 04:30:20 -0700 (PDT)
RECEIVED: from janus.atlas.ripe.net [3] ([193.0.19.13]) by koko.ripe.net [1] with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <atlas@ripe.net>) id 1XC5bZ-0004TU-Nf for colinj@mx5.org.uk; Tue, 29 Jul 2014 13:30:08 +0200
RECEIVED: from localhost.localdomain ([127.0.0.1] helo=janus.atlas.ripe.net [3]) by janus.atlas.ripe.net [3] with esmtp (Exim 4.72) (envelope-from <atlas@ripe.net>) id 1XC5bZ-00004y-IA for colinj@mx5.org.uk; Tue, 29 Jul 2014 11:30:05 +0000
X-RECEIVED: by 10.180.75.230 with SMTP id f6mr41435469wiw.5.1406633431897; Tue, 29 Jul 2014 04:30:31 -0700 (PDT)
RETURN-PATH: <atlas@ripe.net>
RECEIVED-SPF: none (google.com [4]: atlas@ripe.net does not designate permitted sender hosts) client-ip=2001:67c:2e8:11::c100:1348;
AUTHENTICATION-RESULTS: mx.google.com [2]; spf=neutral (google.com [4]: atlas@ripe.net does not designate permitted sender hosts) smtp.mail=atlas@ripe.net
CONTENT-TYPE: text/plain; charset="utf-8"
MIME-VERSION: 1.0
CONTENT-TRANSFER-ENCODING: 7bit
MESSAGE-ID: <20140729113005.32636.40047@janus.atlas.ripe.net>
X-RIPE-SPAM-LEVEL: /
X-RIPE-SPAM-REPORT: Spam Total Points: 0.4 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 4.0 DCC_CHECK Detected as bulk mail by DCC (dcc-servers.net [5])
X-RIPE-SIGNATURE: 407c82a9d3629e01ca957e4b84b7f67191521e4a20cb459dafae86d3fab252b9
Dear colin,
Your probe 2317 has been disconnected since 2014-07-29 10:38:01 UTC.
This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes.
If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/2317/ [6], and click the "edit" button under "Notifications".
Kind regards,
RIPE Atlas Team
Links: ------ [1] http://koko.ripe.net [2] http://mx.google.com [3] http://janus.atlas.ripe.net [4] http://google.com [5] http://dcc-servers.net [6] https://atlas.ripe.net/probes/2317/
-- Best regards, Rene Bartsch, B. Sc. Informatics
Hi, Try to reboot the probe at least by troubleshooting means. Regards. /Alex Saroyan On 07/29/2014 03:34 PM, Colin Johnston wrote:
strange, connectivity seems fine to me at least within BT network range and HSO network range ?
Should I reset the probe or this is a bigger monitoring probe failure ?
Colin
Begin forwarded message:
*From: *RIPE Atlas <atlas@ripe.net <mailto:atlas@ripe.net>> *Subject: **Probe 2317 (home fibre) is disconnected* *Date: *29 July 2014 12:30:05 BST *To: *colin johnston <colinj@mx5.org.uk <mailto:colinj@mx5.org.uk>> *Delivered-To: *colinj@mx5.org.uk <mailto:colinj@mx5.org.uk> *Received: *by 10.70.41.145 with SMTP id f17csp332256pdl; Tue, 29 Jul 2014 04:30:32 -0700 (PDT) *Received: *from koko.ripe.net <http://koko.ripe.net> (koko.ripe.net <http://koko.ripe.net>. [2001:67c:2e8:11::c100:1348]) by mx.google.com <http://mx.google.com> with ESMTPS id f10si19194016wic.74.2014.07.29.04.30.19 for <colinj@mx5.org.uk <mailto:colinj@mx5.org.uk>> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Jul 2014 04:30:20 -0700 (PDT) *Received: *from janus.atlas.ripe.net <http://janus.atlas.ripe.net> ([193.0.19.13]) by koko.ripe.net <http://koko.ripe.net> with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <atlas@ripe.net <mailto:atlas@ripe.net>>) id 1XC5bZ-0004TU-Nf for colinj@mx5.org.uk <mailto:colinj@mx5.org.uk>; Tue, 29 Jul 2014 13:30:08 +0200 *Received: *from localhost.localdomain ([127.0.0.1] helo=janus.atlas.ripe.net <http://janus.atlas.ripe.net>) by janus.atlas.ripe.net <http://janus.atlas.ripe.net> with esmtp (Exim 4.72) (envelope-from <atlas@ripe.net <mailto:atlas@ripe.net>>) id 1XC5bZ-00004y-IA for colinj@mx5.org.uk <mailto:colinj@mx5.org.uk>; Tue, 29 Jul 2014 11:30:05 +0000 *X-Received: *by 10.180.75.230 with SMTP id f6mr41435469wiw.5.1406633431897; Tue, 29 Jul 2014 04:30:31 -0700 (PDT) *Return-Path: *<atlas@ripe.net <mailto:atlas@ripe.net>> *Received-Spf: *none (google.com <http://google.com>: atlas@ripe.net <mailto:atlas@ripe.net> does not designate permitted sender hosts) client-ip=2001:67c:2e8:11::c100:1348; *Authentication-Results: *mx.google.com <http://mx.google.com>; spf=neutral (google.com <http://google.com>: atlas@ripe.net <mailto:atlas@ripe.net> does not designate permitted sender hosts) smtp.mail=atlas@ripe.net <mailto:smtp.mail=atlas@ripe.net> *Content-Type: *text/plain; charset="utf-8" *Mime-Version: *1.0 *Content-Transfer-Encoding: *7bit *Message-Id: *<20140729113005.32636.40047@janus.atlas.ripe.net <mailto:20140729113005.32636.40047@janus.atlas.ripe.net>> *X-Ripe-Spam-Level: */ *X-Ripe-Spam-Report: *Spam Total Points: 0.4 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 4.0 DCC_CHECK Detected as bulk mail by DCC (dcc-servers.net <http://dcc-servers.net>) *X-Ripe-Signature: *407c82a9d3629e01ca957e4b84b7f67191521e4a20cb459dafae86d3fab252b9
Dear colin,
Your probe 2317 has been disconnected since 2014-07-29 10:38:01 UTC.
This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes.
If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/2317/, and click the "edit" button under "Notifications".
Kind regards,
RIPE Atlas Team
On 2014.07.29. 13:34, Colin Johnston wrote:
strange, connectivity seems fine to me at least within BT network range and HSO network range ?
Should I reset the probe or this is a bigger monitoring probe failure ?
Colin
Hello, This morning our IT team executed a planned maintenance in one of our colos, which had a more adverse effect than anticipated. Your probe (as well as ~98% of others) is now connected again. Sorry for the inconvenience, Robert
BTW - I am hosting 6 probes - all 6 have uptime of more then 1 day. Regards. /Alex Saroyan On 07/29/2014 05:07 PM, Robert Kisteleki wrote:
On 2014.07.29. 13:34, Colin Johnston wrote:
strange, connectivity seems fine to me at least within BT network range and HSO network range ?
Should I reset the probe or this is a bigger monitoring probe failure ?
Colin Hello,
This morning our IT team executed a planned maintenance in one of our colos, which had a more adverse effect than anticipated. Your probe (as well as ~98% of others) is now connected again.
Sorry for the inconvenience, Robert
Thanks Robert, that might well have explained it :) Colin On 29 Jul 2014, at 14:07, Robert Kisteleki <robert@ripe.net> wrote:
On 2014.07.29. 13:34, Colin Johnston wrote:
strange, connectivity seems fine to me at least within BT network range and HSO network range ?
Should I reset the probe or this is a bigger monitoring probe failure ?
Colin
Hello,
This morning our IT team executed a planned maintenance in one of our colos, which had a more adverse effect than anticipated. Your probe (as well as ~98% of others) is now connected again.
Sorry for the inconvenience, Robert
A enhancement might be to send second email when connectivity is working ok again ? Colin On 29 Jul 2014, at 16:58, Colin Johnston <colinj@mx5.org.uk> wrote:
Thanks Robert, that might well have explained it :)
Colin
On 29 Jul 2014, at 14:07, Robert Kisteleki <robert@ripe.net> wrote:
On 2014.07.29. 13:34, Colin Johnston wrote:
strange, connectivity seems fine to me at least within BT network range and HSO network range ?
Should I reset the probe or this is a bigger monitoring probe failure ?
Colin
Hello,
This morning our IT team executed a planned maintenance in one of our colos, which had a more adverse effect than anticipated. Your probe (as well as ~98% of others) is now connected again.
Sorry for the inconvenience, Robert
participants (4)
-
Alex Saroyan -
Colin Johnston -
Rene Bartsch -
Robert Kisteleki