[atlas] Problem in status checks?
- Previous message (by thread): [atlas] What is the meaning of 127.0.0.1 as probe resolver?
- Next message (by thread): [atlas] Problem in status checks?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Sat Oct 14 09:11:04 CEST 2017
Error 500 when trying to retrieve status checks: % curl -v 'https://atlas.ripe.net/api/v2/measurements/2060427/status-check?permitted_total_alerts=3' ... > GET /api/v2/measurements/2060427/status-check?permitted_total_alerts=3 HTTP/1.1 > Host: atlas.ripe.net > User-Agent: curl/7.52.1 > Accept: */* > < HTTP/1.1 500 Internal Server Error < Server: nginx/1.10.2 < Date: Sat, 14 Oct 2017 07:09:10 GMT < Content-Type: text/html; charset=utf-8 < Content-Length: 38403 < Connection: keep-alive < Vary: Accept-Encoding, Cookie < X-Frame-Options: SAMEORIGIN < Strict-Transport-Security: max-age=15768000
- Previous message (by thread): [atlas] What is the meaning of 127.0.0.1 as probe resolver?
- Next message (by thread): [atlas] Problem in status checks?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]