-
Notifications
You must be signed in to change notification settings - Fork 735
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
keepalived crashed when reloading, thanks. #118
Comments
@icymoon ,You have a wrong config in keepalived.conf1. As virtual_server_group 192.168.10.x_http1 is not configured, it is still used. Anyway, keepalived really has bug here. I will fix it later. |
I run the test with several wrong config files.. keepalived shouldn't crash with an unused configuration. |
Yes,you are right. But the cofigured svc is in memory. When keepalived is reload, old svc will just try to find their group to compare new group. Bug is just here. You can start keepalived using wrong configured file. That's why i say there is bug here. |
You can just test this by delete unused svc. I have already tried this. |
Thank you very much :) |
Start keepalived with keepalived.conf.1 and reload it with keepalived.conf.2.
It will crashed with segment fault.
The text was updated successfully, but these errors were encountered: