[atlas] Controller kicking out probe with no clear reason?
- Previous message (by thread): [atlas] Controller kicking out probe with no clear reason?
- Next message (by thread): [atlas] Scheduled work on RIPE Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Viktor Naumov
vnaumov at ripe.net
Fri Sep 24 10:12:59 CEST 2021
Hi Ishan, I see that you probe is currently connected and functioning as expected. The problem was that the probe was trying to reconnect to controller too often. For security reason if a probe is trying to connect to controller more than 10 times per hour the throttling kicks in. In such a case I would just stop the probe for an hour and try again. Best regards /vty On 9/24/21 5:44 AM, Ishan Jain wrote: > Hi there, > > > I run a probe with ID, 1001577. I had to restart it few days back and > now it's just not connecting to the controller. It cycles through the > list of controllers, Finds 1 controller it can connect to but that > controller kicks it out. I haven't been able to figure out why this is > happening. I have tried clearing out all the data related to that > probe, restarting it and updating the probe key on the dashboard but > nothing seems to be working. >
- Previous message (by thread): [atlas] Controller kicking out probe with no clear reason?
- Next message (by thread): [atlas] Scheduled work on RIPE Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]