why localhost that doesn t seem right It should be listening rancher-users #k3s

#k3s

Title

# k3s

enough-carpet-20915

10/26/2022, 11:54 PM

why localhost? that doesn’t seem right? It should be listening on the private vlan interface.

creamy-pencil-82913

10/27/2022, 12:09 AM

the flannel interface doesn’t determine what interface etcd listens on

what do the logs show. the etcd startup bits should tell you specifically what address it’s listening on

I will also say, 10.45.0.1 is an odd address. .1 in a subnet is usually the router?

is that really the address assigned to this vlan interface?

enough-carpet-20915

10/27/2022, 12:10 AM

it’s a non-routed subnet

so yes, that’s really the address

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 forever

creamy-pencil-82913

10/27/2022, 12:10 AM

hmm. that will proooobably be OK

so back to the etcd question, what do the logs say about the addresses it’s listening on for peer connections

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"}

that looks right

weird that lsof doesn’t show that

creamy-pencil-82913

10/27/2022, 12:12 AM

there you go. so its got two listeners, one on loopback and one on the actual ip

you’re sure the two nodes can actually reach each other over that private vlan?

enough-carpet-20915

10/27/2022, 12:13 AM

I can ping all other nodes over the vlan

but I can’t get to port 2380

oh, I bet it’s the firewall

Hmm, still not working but I should really go to sleep. I’ll let you know tomorrow if I make any progress.

For whatever reason it worked today after changing the firewall rules last night. Whatever. 😄