IP address 192.168.25.181/24 is down, must be down

[fakhrdeenSalah]

systemctl status vip-manager
● vip-manager.service - Manages Virtual IP for Patroni
Loaded: loaded (/usr/lib/systemd/system/vip-manager.service; enabled; preset: disabled)
Active: active (running) since Wed 2025-04-02 09:29:29 +03; 7min ago
Main PID: 5520 (vip-manager)
Tasks: 11 (limit: 100245)
Memory: 11.2M
CPU: 268ms
CGroup: /system.slice/vip-manager.service
└─5520 /usr/bin/vip-manager --ip=192.168.25.181 --interface=ens160 --netmask=24 --trigger-key=/service/pg_cluster/leader --trigger-value=PGD2 --dcs-type=patroni

Apr 02 09:34:59 PGD2 vip-manager[5520]: 2025-04-02T09:34:59.978+0300 INFO IP address 192.168.25.181/24 is down, must be down
Apr 02 09:35:09 PGD2 vip-manager[5520]: 2025-04-02T09:35:09.978+0300 INFO IP address 192.168.25.181/24 is down, must be down
Apr 02 09:35:19 PGD2 vip-manager[5520]: 2025-04-02T09:35:19.979+0300 INFO IP address 192.168.25.181/24 is down, must be down
Apr 02 09:35:29 PGD2 vip-manager[5520]: 2025-04-02T09:35:29.980+0300 INFO IP address 192.168.25.181/24 is down, must be down
Apr 02 09:35:39 PGD2 vip-manager[5520]: 2025-04-02T09:35:39.981+0300 INFO IP address 192.168.25.181/24 is down, must be down
Apr 02 09:35:49 PGD2 vip-manager[5520]: 2025-04-02T09:35:49.982+0300 INFO IP address 192.168.25.181/24 is down, must be down
Apr 02 09:35:59 PGD2 vip-manager[5520]: 2025-04-02T09:35:59.982+0300 INFO IP address 192.168.25.181/24 is down, must be down
Apr 02 09:36:09 PGD2 vip-manager[5520]: 2025-04-02T09:36:09.983+0300 INFO IP address 192.168.25.181/24 is down, must be down
Apr 02 09:36:19 PGD2 vip-manager[5520]: 2025-04-02T09:36:19.984+0300 INFO IP address 192.168.25.181/24 is down, must be down
Apr 02 09:36:29 PGD2 vip-manager[5520]: 2025-04-02T09:36:29.985+0300 INFO IP address 192.168.25.181/24 is down, must be down

I'm experiencing an issue where the virtual IP address isn't being set on the interface. My setup includes PostgreSQL 17, etcd 3.5.20, and Patroni 3.0.4, but the IP isn't coming up as expected. . The vip-manager logs indicate that the IP is down, and it keeps trying to register it.

Could you please help me troubleshoot this issue?

[pashagolub]

I assume your settings are wrong. You are using patroni rest api but specified trigger key for etcd dcs type

[pashagolub]

Accortding to the manual:

Configuration - Patroni REST API

To directly use the Patroni REST API, simply set dcs-type to patroni and trigger-key to /leader. The defaults for dcs-endpoints (http://127.0.0.1:8008) and trigger-value (200) for the Patroni checker should work in most cases.

[Failon2010]

I have a similar problem, but I made sure that everything seemed to be installed correctly.

● vip-manager.service - Manages Virtual IP for Patroni
Loaded: loaded (/lib/systemd/system/vip-manager.service; enabled; preset: enabled)
Active: active (running) since Wed 2025-05-21 21:46:16 MSK; 1s ago
Main PID: 1205 (vip-manager)
Tasks: 8 (limit: 77104)
Memory: 10.4M
CPU: 9ms
CGroup: /system.slice/vip-manager.service
└─1205 /usr/bin/vip-manager --config=/etc/default/vip-manager.yml

мая 21 21:46:16 gauss-db-node01 vip-manager[1205]: ip : 10.254.0.19
мая 21 21:46:16 gauss-db-node01 vip-manager[1205]: manager-type : basic
мая 21 21:46:16 gauss-db-node01 vip-manager[1205]: netmask : 24
мая 21 21:46:16 gauss-db-node01 vip-manager[1205]: retry-after : 250
мая 21 21:46:16 gauss-db-node01 vip-manager[1205]: retry-num : 2
мая 21 21:46:16 gauss-db-node01 vip-manager[1205]: trigger-key : /leader
мая 21 21:46:16 gauss-db-node01 vip-manager[1205]: trigger-value : gauss-db-node01
мая 21 21:46:16 gauss-db-node01 vip-manager[1205]: verbose : false
мая 21 21:46:16 gauss-db-node01 vip-manager[1205]: version : false
мая 21 21:46:16 gauss-db-node01 vip-manager[1205]: 2025-05-21T21:46:16.147+0300 INFO IP address 10.254.0.19/24 is down, must be down

Tell me what to do.

[pashagolub]

And what is wrong here? Would you please show your config

[Failon2010]

Of course
# config for vip-manager by Cyberte.txt

II'm using debian 12, maybe I don't have any packages to get vip-manager 3.0.0 working for me.

[pashagolub]

would you please paste config here as text, so I don't need to download anything.

@df7cb we do have vip-manager for debian 12, right?

[df7cb]

Yes. Bookworm itself has 1.0.2; apt.postgresql.org has 1.0.2 and 3.0.0 for bookworm.

[Failon2010]

cat /etc/default/vip-manager.yml
# config for vip-manager by Cybertec Schönig & Schönig GmbH

# time (in milliseconds) after which vip-manager wakes up and checks if it needs to register or release ip addresses.
interval: 1000

# the etcd or consul key which vip-manager will regularly poll.
trigger-key: "/leader"
# if the value of the above key matches the trigger-value (often the hostname of this host), vip-manager will try to add the virtual ip address to the interface specified in Iface
trigger-value: "gauss-db-node01"

ip: 10.254.0.19 # the virtual ip address to manage
netmask: 24 # netmask for the virtual ip
interface: ens18 #interface to which the virtual ip will be added

# how the virtual ip should be managed. we currently support "ip addr add/remove" through shell commands or the Hetzner api
hosting-type: basic # possible values: basic, or hetzner.

dcs-type: patroni # etcd, consul or patroni
# a list that contains all DCS endpoints to which vip-manager could talk.
dcs-endpoints:
  - http://10.254.0.20:8008
  # A single list-item is also fine.
  # consul and patroni will always only use the first entry from this list.
  # For consul, you'll obviously need to change the port to 8500. Unless you're using a different one. Maybe you're a rebel and are running consul on port 2379? Just to confuse people? Why would you do that? Oh, I get it.

#etcd-user: "patroni"
#etcd-password: "Julian's secret password"
# when etcd-ca-file is specified, TLS connections to the etcd endpoints will be used.
#etcd-ca-file: "/path/to/etcd/trusted/ca/file"
# when etcd-cert-file and etcd-key-file are specified, we will authenticate at the etcd endpoints using this certificate and key.
#etcd-cert-file: "/path/to/etcd/client/cert/file"
#etcd-key-file: "/path/to/etcd/client/key/file"

# don't worry about parameter with a prefix that doesn't match the endpoint_type. You can write anything there, I won't even look at it.
#consul-token: "Julian's secret token"

# how often things should be retried and how long to wait between retries. (currently only affects arpClient)
retry-num: 2
retry-after: 250  #in milliseconds

# verbose logs (currently only supported for hetzner)
verbose: false