This message was deleted.
# k3sa
adamant-kite-43734
10/26/2022, 11:54 PMThis message was deleted.
c
creamy-pencil-82913
10/27/2022, 12:09 AMthe flannel interface doesn’t determine what interface etcd listens on
creamy-pencil-82913
10/27/2022, 12:09 AMwhat do the logs show. the etcd startup bits should tell you specifically what address it’s listening on
creamy-pencil-82913
10/27/2022, 12:09 AMI will also say, 10.45.0.1 is an odd address. .1 in a subnet is usually the router?
creamy-pencil-82913
10/27/2022, 12:10 AMis that really the address assigned to this vlan interface?
e
enough-carpet-20915
10/27/2022, 12:10 AMit’s a non-routed subnet
enough-carpet-20915
10/27/2022, 12:10 AMso yes, that’s really the address
enough-carpet-20915
10/27/2022, 12:10 AM Copy code
4: enp35s0.4000@enp35s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc noqueue state UP group default qlen 1000
link/ether a8:a1:59:0f:2c:77 brd ff:ff:ff:ff:ff:ff
inet 10.45.0.1/24 brd 10.45.0.255 scope global enp35s0.4000
valid_lft forever preferred_lft forever
inet6 fe80::aaa1:59ff:fe0f:2c77/64 scope link
valid_lft forever preferred_lft foreverc
creamy-pencil-82913
10/27/2022, 12:10 AMhmm. that will proooobably be OK
creamy-pencil-82913
10/27/2022, 12:11 AMso back to the etcd question, what do the logs say about the addresses it’s listening on for peer connections
e
enough-carpet-20915
10/27/2022, 12:11 AM Copy code
Oct 26 23:47:41 homer k3s[26328]: {"level":"info","ts":"2022-10-26T23:47:41.289Z","caller":"embed/etcd.go:581","msg":"serving peer traffic","address":"10.45.0.1:2380"}
Oct 26 23:47:41 homer k3s[26328]: {"level":"info","ts":"2022-10-26T23:47:41.289Z","caller":"embed/etcd.go:581","msg":"serving peer traffic","address":"127.0.0.1:2380"}enough-carpet-20915
10/27/2022, 12:11 AMthat looks right
enough-carpet-20915
10/27/2022, 12:11 AMweird that lsof doesn’t show that
c
creamy-pencil-82913
10/27/2022, 12:12 AMthere you go. so its got two listeners, one on loopback and one on the actual ip
creamy-pencil-82913
10/27/2022, 12:12 AMyou’re sure the two nodes can actually reach each other over that private vlan?
e
enough-carpet-20915
10/27/2022, 12:13 AMI can ping all other nodes over the vlan
enough-carpet-20915
10/27/2022, 12:13 AMbut I can’t get to port 2380
enough-carpet-20915
10/27/2022, 12:13 AMoh, I bet it’s the firewall
enough-carpet-20915
10/27/2022, 12:19 AMHmm, still not working but I should really go to sleep. I’ll let you know tomorrow if I make any progress.
enough-carpet-20915
10/27/2022, 5:53 PMFor whatever reason it worked today after changing the firewall rules last night. Whatever. 😄
2 Views