Skip to main content

Troubleshooting

Troubleshooting: No Data​

Take the following steps:

  1. Check whether the eBPF network module is running.

    Run the following command on each node:

    ps -ef | grep ebpf-network

    If the process exists, the eBPF network module is running. If the process does not exist, the eBPF network module is not running.

  2. Identify why the network module is not enabled.

    Check whether the node kernel version is supported:

    cat /proc/version

    Compare the OS version and kernel version against the support list.

    If the kernel version is within the supported range (later than 4.19.0), check whether the Agent is disabled or whether the circuit breaker is triggered.

    View circuit breaker logs:

    Kubernetes:

    kubectl -n tingyun exec -ti tingyun-linux-agent-vrtwk -- cat /opt/agent/logs/oneagent/watchdog.log

    Linux host:

    cat /opt/tingyun-oneagent/logs/oneagent/watchdog.log

  3. If the network module is running, confirm the Agent status through logs.

    Kubernetes:

    kubectl -n tingyun exec -ti tingyun-linux-agent-vrtwk -- cat /opt/agent/ebpf/logs/ebpf-agent.log

    Linux host:

    cat /opt/tingyun-oneagent/logs/agent/ebpf-network.log

    If data is uploaded successfully, you will see logs similar to:

    2023-04-21 15:09:49.555 (pid:8815,uid:0) INFO Metrics upload Answer http://tingyun-collector.tingyun.svc:7666/ebpfMetrics?version=1.0.0&license=vZIqa8SUREkDAyMQ
    	{"status":"success","result":"ok"}

    If communication with the Collector fails, you may see error logs similar to:

    2023-04-21 15:12:13.602 (pid:20192,uid:0) ERROR http://tingyun-collector.tingyun.svc:7666/ebpfInit?version=1.0.0&license=1234567890 Login Error ConnectFailed

    Check the Collector deployment status and network connectivity.