[atlas] measurements "Forbidden"
- Previous message (by thread): [atlas] measurements "Forbidden"
- Next message (by thread): [atlas] measurements "Forbidden"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marc Anthony Warrior
warrior at u.northwestern.edu
Tue Apr 24 23:17:54 CEST 2018
Thank you for your response, Viktor. Is anyone still running into this issue? I looked at the post regarding this weekend's problems having been resolved, so I tried launching new measurements today (April 24, 2018). However, it seems like I'm still only getting Forbidden statuses on all measurements. Regards, Marc On Tue, Apr 24, 2018 at 4:06 AM Viktor Naumov <vnaumov at ripe.net> wrote: > Hi Marc, > > That happened because of the last weekend message delays issues Chris > wrote about yesterday. > > Your one-off measurement was scheduled and finished before the controllers > got the task on execution. The measurements got the status "Forbidden" > because there were no reaction from controllers within the one-off lifespan > which is ~15 minutes. > > Finally controllers got the task and probes did the measurements but way > later. Therefore you can see RTTs on the Probes tab or > https://atlas.ripe.net/api/v2/measurements/12264107/latest. > > You can get the results from your measurements from the "latest" API or > repeat your measurements. > > Sorry for inconvenience. > wbr > /vty > > > On 4/24/18 2:10 AM, Marc Anthony Warrior wrote: > > The most recent example of this occurrence I have is experiment #12264107, > which has a status of {"error":{"status":403,"code":104,"detail":"This > measurement hasn't yet started or is no longer > running","title":"Forbidden"}}, returned [] for results, and has 40 > responsive / allocated probes of the requested 50. > > On Mon, Apr 23, 2018 at 4:47 PM Marc Anthony Warrior < > warrior at u.northwestern.edu> wrote: > >> All of the measurements of concern are labeled "short_query_experiment" >> in their "description" field. I am attempting to perform "ping" >> measurements, resolved on probe, towards a number of common domains. >> >> More details: All of the measurements indefinitely return a status of >> "{"error":{"status":403,"code":104,"detail":"This measurement hasn't yet >> started or is no longer running","title":"Forbidden"}}" (never done), even >> if the measurement is in face performed and has results, which makes it >> very difficult to determine when a measurement has been successfully >> deployed. >> >> On Mon, Apr 23, 2018 at 4:30 PM Randy Bush <randy at psg.com> wrote: >> >>> > All of my RIPE Atlas measurement requests (pings in this case) are >>> > suddenly failing with a status "title" field value "Forbidden". Why is >>> > this happening? >>> >>> you might get a better answer if you identified the experiment >>> >>> randy >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20180424/fc86a18a/attachment.html>
- Previous message (by thread): [atlas] measurements "Forbidden"
- Next message (by thread): [atlas] measurements "Forbidden"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]