This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] more than 10 concurrent measurements to the same target
- Previous message (by thread): [atlas] more than 10 concurrent measurements to the same target
- Next message (by thread): [atlas] Scheduling a test for all probes?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Viktor Naumov
vnaumov at ripe.net
Sat Dec 12 13:15:43 CET 2015
Hi, On 12/11/15 5:39 PM, Klaus Darilion wrote: > > On 11.12.2015 16:11, Stephane Bortzmeyer wrote: > > I believe that the counter is global (not just your measurements). I > often see this error when measuring 8.8.8.8 (a very popular target). That's absolutely right. > That's what I heard too. But I have the problem when targeting my server > which for sure nobody test except me. I also have the problem even when > all my measurements to this target are already stopped. It seems that > this counter is not updated in real time. > > regards > Klaus > It can happen when you use one-offs. RIPE Atlas infrastructure uses a timeout of ~15 minutes after starting one-off measurement before marking it as finished. You also can check what measurements are/were performed against a particular target on the RIPE Stat on "Activity" tab. Scroll down to the very last "RIPE Atlas measurement target" view. Cheers, /vty
- Previous message (by thread): [atlas] more than 10 concurrent measurements to the same target
- Next message (by thread): [atlas] Scheduling a test for all probes?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]