-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segfault in forwarder on endpoint uninstall #504
Comments
@richardstone Could you enable trace logs in the forwarder https://github.com/networkservicemesh/deployments-k8s/blob/main/apps/forwarder-vpp/forwarder.yaml#L29-L30? Could also you point out what applications are used? (Is it just https://github.com/networkservicemesh/cmd-nse-icmp-responder and https://github.com/networkservicemesh/cmd-nsc or something else?) |
@denis-tingaikin I'll try to reproduce with trace logs, but as this is an intermittent issue, I'm not sure when will that be.. |
@edwarnicke , @ljkiraly , @richardstone I think the best solution here is to try to add testing for VLAN remote case on CI. |
Hello @denis-tingaikin, @edwarnicke, I added more remote vlan mechanism related TCs in pull request https://github.com/networkservicemesh/deployment_k8s#4465 Laszlo |
This issues is still popping up from time to time, it happened again last night. I suspect VPP does not update the timestamp as logs from VPP looks to be having the very same timestamp for all lines it prints. In case of the forwarder where the segfault appeared, the pod was alive from
@edwarnicke Should I open a ticket for the VPP timestamp issue? |
…k-k8s@main PR link: networkservicemesh/sdk-k8s#504 Commit: 51fb1b9 Author: Network Service Mesh Bot Date: 2024-05-15 10:40:06 -0500 Message: - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#504) PR link: networkservicemesh/sdk#1624 Commit: c2a3414 Author: Nikita Skrynnik Date: 2024-05-16 02:24:48 +1100 Message: - Fix some leaks in opa policies (#1624) * Fix some leaks in opa policies * fix go linter issues --------- Signed-off-by: NSMBot <[email protected]>
Forwarder unexpectedly restarted with a segfault when then endpoint got removed.
The issue is rarely reproducible..
NSM component versions are v1.2.0-rc.1
forwarder-vpp-5r59k-forwarder-vpp-prev.txt
The text was updated successfully, but these errors were encountered: