- ripe-atlas - mailman.ripe.net

Re: [atlas] Troubleshooting USB stick issues - reaching out
by Christophe Van Reeth 28 Jul '16

28 Jul '16

Hi, It's not just the Sandisk sticks that go into permanent readonly mode. The Verbatim have the same problem. Mine went into readonly mode after only 10.5 months of service. Kind regards, Christophe Van Reeth > Dear colleagues, > > recently, some of the third version of RIPE Atlas probes have had an > issue with their USB sticks. > > We're still investigating what may be causing this issue, > and in the meantime we have a possible solution, outlined in this RIPE > Labs article (and below in the email) > https://labs.ripe.net/Members/philip_homburg/troubleshooting-ripe-atlas-pro… > > These steps might not be a surprise to the users on this list, > but on the 4th of July we reached out to almost 5000 hosts of > "abandoned" probes, and we see immediate positive results! > > As you can see from some screenshots I quickly made, > number of active probes have increased - from 8883 on 1st July, > to 9323 this morning. Allowing for normal fluctuations, > this is still a considerable increase -- and we are grateful! > > Thank you for all the effort that you put into keeping the > RIPE Atlas network strong by keeping your probes connected. > > Kind regards, > Vesna (and the RIPE Atlas team) > > === > > Steps to power-cycle probe without USB stick: > > 1. Unplug the probe from its power source > 2. Remove the USB stick from the probe > 3. Plug in the probe WITHOUT the USB stick > 4. Wait for ten minutes > 5. Insert the USB stick > > After an hour, check SOS-messages & "Status" tab > > Note: Only on a network with working DHCP. > If you have configured probe to use static IP, > this setting would be lost if trying the steps. > > If this didn't help, try using a new, brand-name USB stick that is at > least 4GB in size (it does not need any preparation but its contents > will be erased so make sure it does not store anything crucial) > > If the problem is still there, please contact us at atlas(a)ripe.net >

1 0

Fwd: Probe 2317 is down (home fibre)
by Colin Johnston 25 Jul '16

25 Jul '16

seems fine to me ? dont have connectivity to ripe site though from BT network range in uk what is telia upto ? Colins-iMac:~ colinj$ traceroute www.ripe.net traceroute to www.ripe.net (193.0.6.139), 64 hops max, 52 byte packets 1 bthomehub (192.168.1.254) 1.913 ms 1.078 ms 1.078 ms 2 * * * 3 * * * 4 31.55.185.196 (31.55.185.196) 16.187 ms 15.477 ms 15.443 ms 5 195.99.127.142 (195.99.127.142) 15.557 ms 195.99.127.130 (195.99.127.130) 16.274 ms 195.99.127.128 (195.99.127.128) 16.602 ms 6 vhsaccess2-pos1-0.faraday.fixed.bt.net (195.99.127.9) 16.979 ms 16.611 ms 195.99.127.25 (195.99.127.25) 17.097 ms 7 166-49-211-240.eu.bt.net (166.49.211.240) 16.413 ms 166-49-211-236.eu.bt.net (166.49.211.236) 16.225 ms 166-49-211-238.eu.bt.net (166.49.211.238) 15.821 ms 8 213.248.82.249 (213.248.82.249) 16.880 ms 15.785 ms 15.470 ms 9 ldn-bb2-link.telia.net (62.115.137.194) 16.633 ms 213.248.82.249 (213.248.82.249) 15.631 ms 15.400 ms 10 ldn-bb3-link.telia.net (80.91.248.90) 15.776 ms ldn-bb2-link.telia.net (213.155.136.62) 16.815 ms adm-bb4-link.telia.net (62.115.142.221) 22.936 ms 11 adm-b2-link.telia.net (62.115.141.51) 25.759 ms adm-b2-link.telia.net (80.91.253.182) 22.263 ms adm-b2-link.telia.net (62.115.141.17) 21.979 ms 12 adm-b2-link.telia.net (80.91.253.182) 22.481 ms adm-b2-link.telia.net (62.115.141.9) 22.344 ms adm-b2-link.telia.net (62.115.141.63) 27.606 ms Colin > Begin forwarded message: > > From: RIPE Atlas (no reply) <no-reply(a)ripe.net> > Subject: Probe 2317 is down (home fibre) > Date: 21 June 2015 20:30:07 BST > To: colinj(a)mx5.org.uk > > Dear Dear colin johnston, > > Your probe 2317 has been disconnected since 2015-06-21 18:49:16 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 > atlas(a)ripe.net

5 7

Identifying widespread outages using atlas?
by Rafal.Jankowski＠thomsonreuters.com 20 Jul '16

20 Jul '16

Hi I'm wondering if there is any good statistic tool that helps identyfing any widespread Internet outages using ripe atlas probes such as ISP issues (like todays http://www.bbc.co.uk/news/technology-36844712), cable cuts, etc. Normally I select probe and look into public measurements but it does not seem to be very effective. ________________________________ This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential. If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and any attachments. Certain required legal entity disclosures can be accessed on our website.<http://site.thomsonreuters.com/site/disclosures/>

2 3

Stop time not retained when creating new measurement
by Bill Fenner 18 Jul '16

18 Jul '16

Hi, I created a new measurement this morning, https://atlas.ripe.net/measurements/4467029/ . Its status says: Timing 2016-07-16 07:35 No stop time defined but I filled in the stop time when I created the measurement via the web page; I saved the command that it gave me to invoke the API and it includes: ... "is_oneoff": false, "bill_to": "fenner(a)fenron.com", "stop_time": 1469361631 } a) this feels like a bug. Is it a bug? b) can I add the stop time post-facto, or should I remember to go back and click "stop"? Thanks, Bill

2 1

start one-off from probe overview page
by Job Snijders 15 Jul '16

15 Jul '16

Hi all, UI feature requests: It would be cool if there is a button to start a one-off measurement from a certain probe's overview pages. If I am at https://atlas.ripe.net/probes/25606/ - would be nice if I can immediately jump into a one-off, rather then copy-pasting the probe's ID and creating a new one-off UDM. Kind regards, Job

1 0

Error creating one-off ping measurement
by Jared Mauch 15 Jul '16

15 Jul '16

We are attempting to test some things and I’m getting this error. "A one-off measurement cannot have the interval field set” It seems to be a problem if this field is even blank, anyone else experience this? - Jared

3 3

Re: [atlas] Is the Atlas probe hackable?
by fuller＠beif.de 14 Jul '16

14 Jul '16

related to? http://mailman.nanog.org/pipermail/nanog/2016-March/084946.html

1 0

Probe down
by Виталий Туровец 14 Jul '16

14 Jul '16

Hello there! I've got a probe #20190 (https://atlas.ripe.net/probes/20190/) and it shows disconnected status it Atlas Web UI. I've tried to reboot the probe, it gets the IP address from my router via DHCP and i can ping it, the probe opens TCP connection to 193.0.19.25:443 and that's it. The question: how do i make it connect to Atlas again? -- ~~~ WBR, Vitalii Turovets Software Engineer VITU-RIPE

2 1

Result streams not working
by Florencia Alvarez Etcheverry 13 Jul '16

13 Jul '16

Hello, I started working with RIPE Atlas last week, when I made a script to create a one-off ping measurement between two specific probes (which I ping to check if they were working). I used Cousteau API, by default I sent 3 packets and I had 5 seconds of timeout. I got the results one time and then it stopped working. I changed the timeout to 3 or 4 minutes and while waiting for the callback function to execute I checked on the webpage and I can see the results for every measure I launched. So I see the results on the page but they don't get to the stream and the callback function is never called. I also saw the status changed from "ongoing" to "stopped" several minutes after I've seen the results; which leads me to another question, when a measurement stops?, why if I already have the results of a ping (that is the only thing I've launched) it's still running? I tried with Cousteau and also directly with socketIO but it has the same behavior. When I took off the parameters "packets=1,interval=60" of the request (leaving default values), I got the result with Cousteau API, but not with the socket directly. When I run it again it didn't work, so it looks like it works one of 20 times. Is there something I could do or am I doing something wrong? Thank you, Florencia. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 6

Troubleshooting USB stick issues - reaching out
by Vesna Manojlovic 11 Jul '16

11 Jul '16

Dear colleagues, recently, some of the third version of RIPE Atlas probes have had an issue with their USB sticks. We're still investigating what may be causing this issue, and in the meantime we have a possible solution, outlined in this RIPE Labs article (and below in the email) https://labs.ripe.net/Members/philip_homburg/troubleshooting-ripe-atlas-pro… These steps might not be a surprise to the users on this list, but on the 4th of July we reached out to almost 5000 hosts of "abandoned" probes, and we see immediate positive results! As you can see from some screenshots I quickly made, number of active probes have increased - from 8883 on 1st July, to 9323 this morning. Allowing for normal fluctuations, this is still a considerable increase -- and we are grateful! Thank you for all the effort that you put into keeping the RIPE Atlas network strong by keeping your probes connected. Kind regards, Vesna (and the RIPE Atlas team) === Steps to power-cycle probe without USB stick: 1. Unplug the probe from its power source 2. Remove the USB stick from the probe 3. Plug in the probe WITHOUT the USB stick 4. Wait for ten minutes 5. Insert the USB stick After an hour, check SOS-messages & "Status" tab Note: Only on a network with working DHCP. If you have configured probe to use static IP, this setting would be lost if trying the steps. If this didn't help, try using a new, brand-name USB stick that is at least 4GB in size (it does not need any preparation but its contents will be erased so make sure it does not store anything crucial) If the problem is still there, please contact us at atlas(a)ripe.net

3 2