[igt-dev] [PATCH i-g-t] docs/chamelium: Document debugging network issues
Khaled Almahallawy
khaled.almahallawy at intel.com
Thu Aug 18 04:15:28 UTC 2022
Some tips on how to debug network issue if Chamelium is not reachable
over the network
Signed-off-by: Khaled Almahallawy <khaled.almahallawy at intel.com>
---
docs/chamelium.txt | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/docs/chamelium.txt b/docs/chamelium.txt
index c4c224689bde..f180e8364d3f 100644
--- a/docs/chamelium.txt
+++ b/docs/chamelium.txt
@@ -185,6 +185,34 @@ On V3:
Chameleon v3 uses systemd to manage the chameleond service. The logs can be
accessed using `$ journalctl -u chameleond`, or the .GetChameleonLogs() XMLRPC call.
+* If Chamelium is not reachable over the network, some options to check:
+
+1- Connect to Chamelium using serial console and make sure a service is
+listening on port 9992 as following:
+
+$ netstat -a -n -t
+Active Internet connections (servers and established)
+Proto Recv-Q Send-Q Local Address Foreign Address State
+tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
+tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
+tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
+tcp 0 0 0.0.0.0:9992 0.0.0.0:* LISTEN
+
+2- Check if a proxy setting prevents the access to Chamelium services from
+ the host where IGT tests are running:
+ $ curl --noproxy '*' 192.168.1.2:9992
+ or using wireshark/tcpdump to see if the HTTP requests forwarded to
+ Chamelium or not:
+ $ tcpdump 'tcp port 9992'
+
+A successful connection can be checked on Chamelium as below:
+
+$ netstat -a -n -t
+Active Internet connections (servers and established)
+Proto Recv-Q Send-Q Local Address Foreign Address State
+tcp 0 0 0.0.0.0:9992 0.0.0.0:* LISTEN
+tcp 0 0 192.168.1.2:9992 192.168.1.9:51530 TIME_WAIT
+
Daemon Source, Build and Deploy [V2 only]
-----------------------------------------
--
2.25.1
More information about the igt-dev
mailing list