This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/

[atlas] Probe not appearing in the Atlas

Previous message (by thread): [atlas] Probe not appearing in the Atlas
Next message (by thread): [atlas] Leaseweb Network (US, Manassas and San Francisco) have joined RIPE Atlas anchors

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Viktor Naumov vnaumov at ripe.net
Wed Oct 28 09:31:35 CET 2015

Hi,

Looks like it has DNS problem. I do not see SOS messages from it, but I 
see it connects to our infrastructure but probably fails to resolve our 
controller.

In addition it triggered a bug i just fixed that prevented it to 
register successfully.  Only new or log time disconnected probes with 
DNS problems were affected.

Cheers,

/vty

On 10/27/15 3:17 PM, Ismael Carmona wrote:
> Hello,
>
> We have the probe  #24142, it gets DHCP fine (91.123.100.8) and we can 
> ping it and see with sflow that it perform requests to external 
> servers but we cannot find it online in the atlas.
>
> We already tried rebooting it.
>
> Any idea how we can make it appear online in the atlas page?
>
> Thank you,
> Ismael
>

Previous message (by thread): [atlas] Probe not appearing in the Atlas
Next message (by thread): [atlas] Leaseweb Network (US, Manassas and San Francisco) have joined RIPE Atlas anchors

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ripe-atlas Archives ]