15335 network_services_controller.go:151] Failed to replace route to service VIP

bsaurusrex

Cadet
Joined
Feb 26, 2022
Messages
7
Keep seeing this in syslog. Can anyone give me an idea what it means?

Feb 26 17:15:59 freenas env[15335]: E0226 17:15:59.138777 15335 network_services_controller.go:151] Failed to replace route to service VIP 192.168.1.103 configured on kube-dummy-if. Error: exit status 2, Output: RTNETLINK answers: File exists
 

Milkysunshine

Dabbler
Joined
Mar 1, 2022
Messages
16
Same issue. Very frequent reports
Code:
Mar  6 10:42:28 zion env[2645126]: E0306 10:42:28.484147 2645126 network_services_controller.go:151] Failed to replace route to service VIP 192.168.XX.XX configured on kube-dummy-if. Error: exit status 2, Output: RTNETLINK answers: File exists
 

as2008

Cadet
Joined
Mar 9, 2022
Messages
1
Same here, trying to start syncthing from truecharts:
Mar 9 14:23:32 frida-truenas env[583707]: E0309 14:23:32.252862 583707 network_services_controller.go:151] Failed to replace route to service VIP 192.168.xxx.xxx configured on kube-dummy-if. Error: exit status 2, Output: RTNETLINK answers: File exists
 

TurtleFX

Dabbler
Joined
Nov 20, 2018
Messages
11
Same here, using Syncthing and Plex apps from TrueCharts on TrueNAS-SCALE-22.02.0
Code:
Mar 13 15:20:34 truenas env[12886]: E0313 15:20:34.143175   12886 network_services_controller.go:151] Failed to replace route to service VIP 192.168.10.10 configured on kube-dummy-if. Error: exit status 2, Output: RTNETLINK answers: File exists
 

mevans336

Dabbler
Joined
Aug 16, 2016
Messages
23
If anyone else has this issue, because I still was as of the latest version.

You can fix it like so:

1. Apps - Settings - Advanced
2. Set the 'Route v4 Interface'
3. Set the 'Route v4 Gateway'

After that, the errors spamming my log ceased.
 

scr

Cadet
Joined
Oct 26, 2022
Messages
1
I've the same error message even when I set 'Node IP' to the bridge IP (192.168.1.4), 'Route v4 Interface' to br01 and 'Route v4 Gateway' to my router address (192.168.1.1):
Code:
10830 network_services_controller.go:193] Failed to replace route to service VIP 192.168.1.4 configured on kube-dummy-if. Error: exit status 2, Output: RTNETLINK answers: File exists


Setting up 'Node IP' to 0.0.0.0 makes no changes to error message.
Output of 'ip a' command (20+ kube-bridge entries were skipped for clarity):

Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br01 state UP group default qlen 1000
    link/ether a8:a1:59:3d:4e:4c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::aaa1:59ff:fe3d:4e4c/64 scope link
       valid_lft forever preferred_lft forever
3: br01: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b2:aa:95:14:81:19 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.4/24 brd 192.168.1.255 scope global br01
       valid_lft forever preferred_lft forever
4: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br01 state UNKNOWN group default qlen 1000
    link/ether fe:a0:98:5d:81:b6 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fca0:98ff:fe5d:81b6/64 scope link
       valid_lft forever preferred_lft forever
5: kube-bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 86:45:29:03:71:c3 brd ff:ff:ff:ff:ff:ff
    inet 172.16.0.1/16 brd 172.16.255.255 scope global kube-bridge
       valid_lft forever preferred_lft forever
    inet6 fe80::20f8:a1ff:fe12:cc07/64 scope link
       valid_lft forever preferred_lft forever
6: kube-dummy-if: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
    link/ether 9e:08:2b:d7:b2:a1 brd ff:ff:ff:ff:ff:ff
    inet 172.17.68.199/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.0.10/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.189.62/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.221.40/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.198.64/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.73.217/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.235.9/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.167.35/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.127.231/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.216.85/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.94.206/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.200.210/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.0.1/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 172.17.40.67/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet 192.168.1.4/32 scope link kube-dummy-if
       valid_lft forever preferred_lft forever
    inet6 fe80::68b7:31ff:fed0:f72d/64 scope link
       valid_lft forever preferred_lft forever
 
Top