https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
Bad return code from 'ipset list -name'. error=exit status 1 family="inet" stderr="ipset v7.21: Cannot open session to kernel.\n"
That would seem to indicate a problem with the kernel or ipset binary. But not one that I’ve seen before, no.
What kind of node is this running on?
Is this a real node or some sort of paravirtualized container thing?
b
real node
single node
c
can you run that same command on the base OS?
what kind of kernel are you running?
b
Linux node Thu Sep 4 20:28:16 EDT 2025 x86_64 GNU/Linux
c
wheres the rest of it
uname -a
?
b
Linux {{ hostname }} 5.4.297-1-1 #1 SMP Thu Sep 4 20:28:16 EDT 2025 x86_64 GNU/Linux
c
and what distro?
b
uh, "other"
c
This looks like a custom kernel config, as opposed to something maintained by a distro that we might have tested on. Did you forget to include ipset support?
b
Copy code
CONFIG_IP_SET=m
CONFIG_IP_SET_MAX=256
CONFIG_IP_SET_BITMAP_IP=m
CONFIG_IP_SET_BITMAP_IPMAC=m
CONFIG_IP_SET_BITMAP_PORT=m
CONFIG_IP_SET_HASH_IP=m
CONFIG_IP_SET_HASH_IPMARK=m
CONFIG_IP_SET_HASH_IPPORT=m
CONFIG_IP_SET_HASH_IPPORTIP=m
CONFIG_IP_SET_HASH_IPPORTNET=m
CONFIG_IP_SET_HASH_IPMAC=m
CONFIG_IP_SET_HASH_MAC=m
CONFIG_IP_SET_HASH_NETPORTNET=m
CONFIG_IP_SET_HASH_NET=m
CONFIG_IP_SET_HASH_NETNET=m
CONFIG_IP_SET_HASH_NETPORT=m
CONFIG_IP_SET_HASH_NETIFACE=m
CONFIG_IP_SET_LIST_SET=m
CONFIG_NET_EMATCH_IPSET=m
c
is it loaded?
b
Copy code
ip_set_hash_net        36864  3
ip_set_hash_ip         36864  1
ip_set                 45056  3 ip_set_hash_ip,xt_set,ip_set_hash_net
nfnetlink              16384  7 nfnetlink_acct,nf_conntrack_netlink,ip_se
oh looks like it unwedged here:
Copy code
2025-09-30 09:18:26.933 [PANIC][98123] felix/ipsets.go 379: Failed to update IP sets after multiple retries. family="inet"
2025-09-30 09:18:26.993 [INFO][98245] felix/daemon.go 132: Felix starting up GOMAXPROCS=255 builddate="2025-07-31T07:32:47+0000" gitcommit="cf50b562271b7c2ad896af0488d48eddabbb74eb" version="v3.30.2"
2025-09-30 09:18:28.175 [PANIC][98245] felix/ipsets.go 379: Failed to update IP sets after multiple retries. family="inet"
2025-09-30 09:18:28.236 [INFO][98400] felix/daemon.go 132: Felix starting up GOMAXPROCS=255 builddate="2025-07-31T07:32:47+0000" gitcommit="cf50b562271b7c2ad896af0488d48eddabbb74eb" version="v3.30.2"
2025-09-30 09:23:51.848 [INFO][81] felix/daemon.go 132: Felix starting up GOMAXPROCS=255 builddate="2025-07-31T07:32:47+0000" gitcommit="cf50b562271b7c2ad896af0488d48eddabbb74eb" version="v3.30.2"
2025-09-30 09:26:30.211 [INFO][764] felix/daemon.go 132: Felix starting up GOMAXPROCS=255 builddate="2025-07-31T07:32:47+0000" gitcommit="cf50b562271b7c2ad896af0488d48eddabbb74eb" version="v3.30.2"
this may be a red herring. Not sure what causes it.
c
Something weird with your kernel, I suspect.
b
could be
but I just noticed I was looking at rotated logs
the problem I am looking at is that nginx ingress does not come up
l
Our issue of calico-node -felix-ready failing was resolved by switching to ubuntu 22.04. I havent looked further into why 24.04 would start having this issue in 1.30, when it was fine in 1.29 (again, perhaps vxlan)
c
hmm, interesting. we do much testing on 24.04, my main dev workstation is 24.04, and I’ve never seen that.
but then I’m not running a custom kernel build either, as Ben is.
8 Views
Open in Slack
PreviousNext
Powered by