Thank you for your information. I managed to get the probe back online in the meantime (I tried the USB resetting) and it seems to work fine.
Again, thanks. On Sun 1. Jul 2018 at 16:38, Viktor Naumov <[email protected]> wrote: > Hi Andre, > > During the back-end problems we got probes unevenly distributed across > controllers. Lots of probes went to ams14 and started dumping results > they collected being offline. The ams14 is the most powerful controller > and it went online first. Therefore it was highly biased to attract > disconnected probes. It caused major controller slowdown and we decided > to speed up the redistribution process by manually disconnecting some > probes away from ams14. Most likely your probe was one of the innocent > victims. > > Sorry for the inconvenience > > wbr > /vty > > On 7/1/18 2:21 AM, Andre Heinrichs wrote: > > Hi everyone, > > > > Another day, another weird effect. My probe (29384) keeps losing its > > connection to the Atlas systems. That seems to happen since the > > backend problems from Saturday were fixed. I also noticed that my > > probe switched from ctr-nue13 which it was always connected with to > > ctr-ams15 after 18 June and yesterday it got connected to ctr-ams14 > > but lost that connection again quite fast. > > > > My questions again: is that (probes getting disconnected all the time) > > something anyone else sees? Is there something on Atlas‘ side wrong or > > has my probe somehow lost the ability to stay connected for periods of > > more than a couple of minutes? There are again no obvious problems > > with my internet connection. > > > > TIA, > > Andre > > >
