-
-
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
fifo_write_vrrp_states_on_reload not always working #2359
Comments
After further testing, the following pattern has shown itself: A reload in BACKUP state works as expected, at least no change of the statefile is observed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Situation:
Two servers in keepalived vrrp instance; to add or remove IPs from virtual_ipaddress_excluded, reloading occurs regularly.
State changes are written to a statefile by notify_fifo_script, if the script exits, it writes "not running" to the file.
Problem:
Sometimes, after a reload, the statefile shows "not running", but keepalived is working and well. If reloading again, the statefile stays the same.
To Reproduce
Any steps necessary to reproduce the behaviour:
Expected behavior
fifo_write_vrrp_states_on_reload should result in the current state being written to the statefile on reload, always. Even if some obscure situation results in the statefile failing, a repeated reload should correct the issue.
Keepalived version
Distro (please complete the following information):
Details of any containerisation or hosted service (e.g. AWS)
VMware on-premises
Configuration file:
Notify and track scripts
notify_fifo_state.sh.txt
System Log entries
logfile.txt
Did keepalived coredump?
No.
Additional context
I was pleased to see the added functionality for fifo notifying in v2.2.8 and installed it even though it was not considered debian stable yet. For the most part, it works and I am happy to have this feature, unfortunately, sometimes it fails.
The text was updated successfully, but these errors were encountered: