You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, I have not tested everything here. I have to agree with @sebastiangrill's last comment:
When a leader is changed, the new IP address is now assigned locally, but is not published on the network. This means that the system is not accessible for clients.
The system is only accessible via the VIP when I perform a manual arping.
Dec 27 11:40:23 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:23 IP address 10.139.128.48/23 state is false, desired false
Dec 27 11:40:33 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:33 IP address 10.139.128.48/23 state is false, desired false
Dec 27 11:40:43 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:43 IP address 10.139.128.48/23 state is false, desired false
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 current leader from DCS:
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 current leader from DCS: scm-pgsql-01
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 IP address 10.139.128.48/23 state is false, desired true
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 Problems with producing the arp client: no IPv4 address available for interface
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 Problems with producing the arp client: no IPv4 address available for interface
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 Couldn't create an Arp client: no IPv4 address available for interface
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 Configuring address 10.139.128.48/23 on ens224
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 No arp client available, skip send gratuitous ARP
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 IP address 10.139.128.48/23 state is true, desired true
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 IP address 10.139.128.48/23 state is true, desired true
Dec 27 11:41:03 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:41:03 IP address 10.139.128.48/23 state is true, desired true
We use vip-manager 2.8.0 from the pgdg repository.
I hope for help.
Thank you very much
André
The text was updated successfully, but these errors were encountered:
Hello,
I would like to refer again to the following request of mine:
https://github.com/cybertec-postgresql/vip-manager/issues/245
Unfortunately, I have not tested everything here. I have to agree with @sebastiangrill's last comment:
When a leader is changed, the new IP address is now assigned locally, but is not published on the network. This means that the system is not accessible for clients.
The system is only accessible via the VIP when I perform a manual arping.
We use vip-manager 2.8.0 from the pgdg repository.
I hope for help.
Thank you very much
André
The text was updated successfully, but these errors were encountered: