-
-
Notifications
You must be signed in to change notification settings - Fork 732
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
Segmentation fault on keepalived #2350
Comments
It appears that your keepalived is build on a system with Linux 4.15.7 kernel headers, but you are running on a kernel with 4.14.67 headers. This is not valid, since keepalived determines what kernel functionality is available based on the kernel headers it is built against. It may not matter in this case, but it might be the cause of your problem. Another potential issue is that the version of keepalived you are running is very nearly 4 years old, and we might have fixed the issue between then and now (however, I have not seen this problem before and so it is unlikely). What is most interesting is the log message: I think you need to resolve the Netlink "Cannot allocate memory" error, and ensure that keepalived is not built with newer kernel than it is being run on. I will try some test code to see what happens if a link-local address is not added, and see if I can generate a segfault. It would also be helpful if you could provide a copy of your configuration. |
Thanks for looking into the issue . Copy of the configs given below: global_defs |
I have simulated failing to add a link-local address to the VMAC for VI_1_3200_6_la7.3200, since I cannot reproduce the ENOMEM problem. Although I have not been able to reproduce the segfault, it is clear that the code is not handling the failure to add the link-local address. Commit 0b3265b handles failure to add an IPv6 link-local address to a VMAC. Commit e73702a stops an error being logged for failure to send an advert after the IPv6 link-local address has been removed from the VMAC (this isn't directly relevant to this issue, but the problem was noticed when testing this issue). |
Describe the bug
keepalived gave segmentation fault during reload
To Reproduce
Configured 16 dual stack VRRP instance . Did card reload on HA system . Did card reload again on new active
Expected behavior
No segmentation fault
Keepalived version
Keepalived v2.0.19 (10/19,2019)
Copyright(C) 2001-2019 Alexandre Cassen, acassen@gmail.com
Built with kernel headers for Linux 4.15.7
Running on Linux 4.14.67-yocto-standard #1 SMP Tue Sep 26 01:54:37 UTC 2023
A full copy of the configuration file, obfuscated if necessary to protect passwords and IP addresses
If any notify or track scripts are in use, please provide copies of them
Full keepalived system log entries from when keepalived started
Yes , but symbol table was not proper. I tried to take the diff of _start and tried to get the correct symbols manually
The text was updated successfully, but these errors were encountered: