Similar issue here at the moment with probe 1000331; 5020 Centos 8 repo build; On Fri, 5 Jun 2020 at 01:21, Philip Homburg <philip.homburg@ripe.net> wrote:
Hi Jan,
On 2020/06/04 17:01 , Jan Pavlinec wrote:
Can you please check probes IDs (1000585, 1000243) and what it took so long to show that it is connected? Both of those probes were shown as connected at the same time - 20:22) on Tuesday? We noticed that in some cases if you were using the latest version 5020 and register a new probe, it is working within a few minutes.
In reg_init_reply.txt were following data: WAIT TIMEOUT 115
Do you know how to debug it more?
In general, this means that the probe was refused due to a temporary problem. There are two ways this can happen. One is that the probe is doing something wrong, for example connecting way too often. The other is that there is an issue on our end.
There is no reason to worry about network connectivity in the case.
I checked probe 1000243 and in this case there was something weird going on on our end. I'll try to figure out what is happening.
Philip