-
-
Notifications
You must be signed in to change notification settings - Fork 730
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 when reloading from a config without enable_snmp_vrrp to one with it #2086
Comments
I have been able to reproduce this segfault, and can merge a patch that will stop this particular problem. However, what I haven't been able to get working yet is With the current code (plus patch to stop segfault), net-snmp complains, when re-enabling SNMP, that the mibs are already registered. I have added If anyone has any ideas about what needs to be done, then any help would be gratefully received. |
Describe the bug
Keepalived 2.2.7 (and at least some previous versions) segfaults when reloading from a config without enable_snmp_vrrp to one with it.
To Reproduce
enable_snmp_vrrrp
enable_snmp_vrrrp
pid X exited due to segmentation fault (SIGSEGV)
)Note that what dies is the VRRP child process; keepalived's main process reports that and starts it again, but the consequences aren't nice when it happens on a master node (causes the backup node to go to master, then eventually the cluster recovers but meanwhile there is some downtime)
Expected behavior
No segfaults while reloading keepalived.
Keepalived version
Distro (please complete the following information):
Details of any containerisation or hosted service (e.g. AWS)
N/A
Configuration file:
Notify and track scripts
N/A
System Log entries
When SIGHUP is sent after uncommenting
enable_snmp_vrrp
:Did keepalived coredump?
Yes, coredumpctl debug bt follows:
Additional context
N/A
The text was updated successfully, but these errors were encountered: