Replies: 6 comments 5 replies
-
If we are to be able to try and understand what is happening, we will need to following information:
Once you have provided these, it will either tell us what further information we need, or we may be able to identify the cause of the problem. |
Beta Was this translation helpful? Give feedback.
-
version info
keepalived.conf
check_health_for_ftp.sh
keepalived.logMar 07 16:21:51 localhost.localdomain systemd[1]: Starting LVS and VRRP High Availability Monitor... NetworkManager logMar 07 16:20:04 localhost.localdomain NetworkManager[1431]: [1741335604.6124] manager: (ens192): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) |
Beta Was this translation helpful? Give feedback.
-
See also issue #2528 although this isn't relevant if you don't have commit b48f005 included in your code (it was merged after v2.3.2). |
Beta Was this translation helpful? Give feedback.
-
#2277 the scene sounds just mine, persistent FAULT state, but the networkManager log above shows that the base interface is already ok. |
Beta Was this translation helpful? Give feedback.
-
Can you please try keepalived v2.3.3. It has a number of fixes for persistent fault states. |
Beta Was this translation helpful? Give feedback.
-
It is possible that v2.3.3 may not solve the problem for you since you are using such an old kernel. Some of the fixes rely on using IP_FREEBIND socket option on raw sockets, which wasn't supported until kernel 5.17. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
just like the title, it really confused me, if anyone come into this problem?
Beta Was this translation helpful? Give feedback.
All reactions