Send debugging information to support
Gather debugging information
If you have gone through the steps above and the issue is still unresolved, use the debug scripts below to collect a full diagnostic snapshot of your system. Run the appropriate script(s) for the component(s) having issues, then send us the terminal output and the log files generated alongside it.
Note: The scripts must be run as root.
QoS Agent
wget https://api.latence.ca/software/lti_qos-agent-debug.sh
sudo bash lti_qos-agent-debug.sh 2>&1 | tee lti_qos-agent-debug-output.txt
The script will:
- Show the agent's container status, agent ID, reflector IP, and analyzer IP
- Capture traffic in both directions between the agent and the reflector (HTTP, HTTPS, TCP, UDP, TWAMP)
- Verify that data is being sent to the analyzer on port 12092
- Run an iPerf3 test against the reflector
- Report any errors found in the container logs
- Print the routing table and active connections
- Save the full agent container logs to a
.txtfile
Send us lti_qos-agent-debug-output.txt and the generated lti_qos-agent_logs.txt.
Reflector
wget https://api.latence.ca/software/lti_reflector-debug.sh
sudo bash lti_reflector-debug.sh 2>&1 | tee lti_reflector-debug-output.txt
The script will:
- Show the reflector container status and ID
- Capture traffic on all reflector ports to verify what is being received and what is being sent back (HTTP, HTTPS, TCP, UDP, TWAMP)
- Print the routing table and active connections
- Save the full reflector container logs to
lti_reflector_logs.txt
Send us lti_reflector-debug-output.txt and lti_reflector_logs.txt.
Analyzer
cd lti_analyzer
wget https://api.latence.ca/software/lti_analyzer-debug.sh
sudo bash lti_analyzer-debug.sh 2>&1 | tee lti_analyzer-debug-output.txt
The script will:
- Show the status of all analyzer containers (Kafka, InfluxDB, Telegraf, Grafana, Influx-Writer, Anomaly Detection, LatenceTech API, MCP, Chatbot API, etc.)
- Check all analyzer ports (Kafka 12092, InfluxDB 12086, Grafana 12021, API 12099, MCP 12098)
- Capture incoming Kafka traffic to identify which agent IPs are sending data
- Check InfluxDB health and write activity
- Analyze the influx-writer logs for Kafka connectivity and data flow status
- Report errors across all containers
- Print resource usage, routing table, and active connections
- Save each container's logs to individual
.txtfiles
Send us lti_analyzer-debug-output.txt and all the *_logs.txt files generated in the directory.