deepflowio
[BUG] process tap side not shown in Rocky Linux 9
Search before asking
- [X] I had searched in the issues and found no similar feature requirement.
DeepFlow Component
Agent
What you expected to happen
for one outgoing http request, there should be one client nic and one client process flow report, like those in
centos 7
but on Rocky Linux, with the same agent version and agent group config, it only shows client porcess flow
How to reproduce
just install deepflow-agent on Rocky Linux 9 VM, and try to issue the flowing command, then go to *Application Request Log" dashboard and check the result
curl -v http://deepflow.io/docs/zh/
DeepFlow version
Name: deepflow-server community edition Branch: v6.4 CommitID: f0138292a20465b210b8b2decf93ab44b5d37e16 RevCount: 9769 Compiler: go version go1.20.14 linux/amd64 CompileTime: 2024-04-02 09:32:40
Name: deepflow-agent community edition Branch: v6.5.3 CommitId: cfb3560378f755d37bb9b9c1e41305483b0eff4e RevCount: 9935 Compiler: rustc 1.75.0 (82e1608df 2023-12-21) CompileTime: 2024-03-27 02:15:1
DeepFlow agent list
ID NAME TYPE CTRL_IP CTRL_MAC STATE GROUP EXCEPTIONS REVISION UPGRADE_REVISION 1 172.16.49.16-V2 K8S_VM 172.16.49.16 52:54:00:66:87:0a NORMAL default v6.4 9770 10 cvm-lab-rocky9-W7 CHOST_VM 172.16.81.149 52:54:00:7d:53:a6 NORMAL cvm v6.5.3 9935 11 cvm-lab-c7-W5 CHOST_VM 172.16.82.231 52:54:00:c8:81:2e NORMAL cvm v6.5.3 9935
Kubernetes CNI
No response
Operation-System/Kernel version
rocky linux 9: 5.14.0-362.24.1.el9_3.x86_64 centos 7: 3.10.0-1160.114.2.el7.x86_64
Anything else
No response
Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
@curu Thanks for your question. Please check the deepflow-agent log to see if eBPF has any warnings.(On rocky linux 9)
cat /proc/{deepflow-agent PID}/root/var/log/deepflow-agent/deepflow-agent.log | grep eBPF
@curu Thanks for your question. Please check the deepflow-agent log to see if eBPF has any warnings.(On rocky linux 9)
cat /proc/{deepflow-agent PID}/root/var/log/deepflow-agent/deepflow-agent.log | grep eBPF
no warnings. log attached. ebpf.log
Hello, on the other hand, I see that your deepflow-server and deepflow-agent versions are not consistent. In most cases, the server version is allowed to be greater than the agent version, but the agent version is not allowed to be greater than the server version. You can try it first. Synchronize the version. The current v6.4 version is the LTS version. If your agent is not deployed in k8s, you can directly take out the deepflow-agent process from the agent container of the v6.4 image and deploy it on the host.
