- Print
- PDF
Checking if Roadrunner is Configured Properly
For the agents to connect properly, Roadrunner must listen on the proper management and data ports. By default, these are respectively 55777 and 55888.
Check Roadrunner Logs
When roadrunner starts it will display what is received a configuration and should display that it’s listening on the 55777 and 55888 ports.
When create the Roadrunner connector in Skylight the "SensorAgent" datasource must be selected. At that time it is possible to change the default ports
$ sudo docker logs <Roadrunner Container ID>
[...]
14:17:49.921 connect ▶ INFO 00e Successfully connected to DataHub (meta connection) on host: myinstance.analytics.accedian.io in zone: myzone for tenant: 0471ffb8-c000-41ac-9ed8-3da45c696e36.
14:17:49.921 getConfig ▶ INFO 00f Requesting config from DH on host: myinstance.analytics.accedian.io in zone: myzone for tenant: 0471ffb8-c000-41ac-9ed8-3da45c696e36
[...]
14:18:52.101 processMetaMsg ▶ INFO 03d Received config from DH on host: myinstance.analytics.accedian.io in zone: myzone
[...]
14:17:52.951 func1 ▶ INFO 026 server OpenMetricsPushGateway listening on 0.0.0.0:55888 with TLS enabled
[...]
14:17:52.952 func1 ▶ INFO 033 server AgentProxy listening on 0.0.0.0:55777 with TLS enabled
Line 3: Roadrunner connections to Analytics backend.
Line 4: Roadrunner request its configuration.
Line 6: Roadrunner received its configuration.
Line 8: Roadrunner is listening on port 55888.
Line 10: Roadrunner is listening on port 55777.
Note: If the logs only show requests for configuration, that is an indication that Roadrunner is not receiving its configuration.
Using netstats (in container)
The linux tool netstats can be used to determine if Roadrunner is listening on the 55777 and 55888 ports. This needs to be done within the container.
Option | Description |
---|---|
-l | Show listening ports. |
-p | Show the program that opened the socket. |
-t | Show TCP ports. |
-n | Display numeric values for ports, IPs, etc. |
$ sudo docker exec -it <roadrunner container id> netstat -nplt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:10001 0.0.0.0:* LISTEN 1/adh-roadrunner
tcp 0 0 :::55888 :::* LISTEN 1/adh-roadrunner
tcp 0 0 :::55777 :::* LISTEN 1/adh-roadrunner
CAUTION: This operation must be done in the container!
Checking Exposed Ports
For the agents to connect the proper ports must be exposed by docker and a proper port forwarding configured.
Using the command “docker ps” the exposed ports are displayed under the “PORTS” column.
In the example below we can see that the ports are exported for IPv4 and IPv6.
Port Mapping | Description |
---|---|
0.0.0.0:55777->55777/tcp | IPv4 management port |
:::55777->55777/tcp | IPv6 management port |
0.0.0.0:55888->55888/tcp | IPv4 data port |
:::55888->55888/tcp | IPv6 data port |
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
32b9a88ded4e gcr.io/npav-172917/adh-roadrunner:0.372.0 "/docker-entrypoint.…" 17 minutes ago Up 17 minutes 0.0.0.0:55777->55777/tcp, :::55777->55777/tcp, 0.0.0.0:55888->55888/tcp, :::55888->55888/tcp aod-connector-for-myinstance.analytics.accedian.io-myzone
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks