New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
K3s Install on Raspberry Pi 4b failed (TLS Handshake Timeout pi3, pi4, etc) #970
Comments
I upgraded yesterday |
Workaround is to downgrade |
I have the same problem with raspberrypi model 3B+ (version k3s 0.10.0) but with the 0.9.1 it's working. |
Same as above ^ first time attempting to setup, v0.10.0 bugged out, downgrade to 0,9,1 worked 👍 |
Same for Raspberry Pi 3 / 3B with v0.10.1, but 0.9.1 works. Somebody please adjust the issue's title: "K3S Install on Raspberry Pi fails since v0.10.0" |
Related to #869? Spotted the same error message there. |
And #556 as already linked here. Haven't really been able to find a reproducible case. |
|
Same issue with k3s version v0.10.1 (7d650d3) on Intel/Amd64. (Manually copied k3s v0.10.1 from releases into VirtualBox VM with Ubuntu 18.04.3) The exact error message is: FATA[2019-10-30T16:52:21.768049354+01:00] starting tls server: Get https://127.0.0.1:6444/apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions: net/http: TLS handshake timeout k3s v0.9.1 starts on the same VM without this error. |
@gocursor your problem could be a general networking problem, maybe not directly related to this arm issue. |
@erikwilson I re-imaged OS as Ubuntu 19.10 64bit on my Raspberry Pi4, and then tried again, issue is the same as previous, "TLS handshake timeout". Below information you probably need: K3s version:
OS version:
Arch version:
entropy_avail:
Error Logs:
|
Same on a recent https://github.com/hypriot. |
Also tried to install old version v0.9.1, first time failed with cgroup error:
After add the two option of cgroup into /boot/firmware/config.txt file, and tried again, it succeed.
After that, I tried to upgrade K3s to latest version, it succeed this time:
If I have time, will tried to directly install the latest version of K3s with the two cgroup option on a fresh Ubuntu 19.10 OS. At least I can run latest K3s on my Raspberry Pi4. |
Thanks for testing & the data points @gm12367! Interesting, I would expect k3s v0.10.1 to error out with the same memory cgroup message as v0.9.1. 401 bytes of entropy is pretty low, would think there would be a crypto error instead of handshake timeout, but if possible please try to reproduce with the |
Same on a Rock64 with Armbian:
After downgrading to k3s version v0.9.1 it worked. |
Same problem here on openSUSE 15.1 ARM64 (RPi3) |
When I do a get request to the api server on the secure port I get the following output.
|
@erikwilson Today I found k3s version update to v0.10.2, and now it can install on Raspbian Buster successfully, don't know if the new version include the fix. I also tried with v0.10.1 and succeed as well. So I don't know if there is something changed. |
Still no success with 0.10.2 on a RPi 3B+. Same TLS handshake timeout error as above. What "cgroup option" are you referring to? |
@m0wlheld "cgroup_memory=1 cgroup_enable=memory", I mentioned in my previous reply, you can add it into config.txt and try again |
@gm12367 Okay, I have that in my /boot/cmdline.txt (see below), still no success with any version > 0.9.1
|
Same here. Couldn't get any v0.10.x working on rpi3b+ with raspbian up-to-date (even with |
Running |
downgrading to k3s version 0.9.1 worked for me too. Running on RPi 3B+ with OS:
The error I got on version 0.10.2 and 0.10.0 was |
There's a race condition happening starting the apiserver and waiting for crds to be created. In |
$ k3s --version failed on RPI3.
|
@xiaods I have install rng-tool and set the swapaccount=1 as @zimme comment
|
For what it is worth, it is recommended for kubernetes nodes to have swap disabled, but probably especially important for the RPi3 with poor i/o, as once the system starts swapping it can slow to a crawl. |
@pierremahot my os is hypriotos, it default have no rng-tools. i follow this instruct :https://www.nico-maas.de/?p=1562 to install rng-tools. the rpi4 it works, but rpi3 not working . if i let rpi3 as agent, it raised a error:
|
No movement on this in a while (Nov 2019) @erikwilson any thoughts on next steps on this issue? |
Hi, just for update I am now using actualy k3s version v1.17.3+k3s1 (5b17a17) (work very well) and I don't have any problème on this issue since v1.13 if i remember. |
v1.17.4+k3s1 does not work for me in similar circumstances, so this isn't fixed in modern releases. |
v1.18.2+k3s1, 5.6.14-300.fc32.aarch64, rpi3 - same problem. I also added "cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory" but this makes no difference. |
I'm having this issue too on ubuntu 64 on Pi 3 and 3+ |
@aceslick911 can you open a new issue and fill out the template so that we can assist in diagnosing your problem? |
This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions. |
Thanks for helping us to improve k3s! We welcome all bug reports. Please fill out each area of the template so we can better help you. You can delete this message portion of the bug report.
Version:
Provide the output from
k3s -v
and provide the flags used to install or run k3s server.OS version:
Linux raspberrypi 4.19.75-v7l+ rancher/k3s#1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l
bootloader version:
Describe the bug
A clear and concise description of what the bug is.
After run install command "curl -sfL https://get.k3s.io | sh -", installation can't be completed, and TLS handshake timeout error prompted
To Reproduce
Steps to reproduce the behavior:
Run command 'curl -sfL https://get.k3s.io | sh -' on Raspberry Pi 4b 4G memory
Expected behavior
A clear and concise description of what you expected to happen.
Actual behavior
A clear and concise description of what actually happened.
TLS handshake timeout
Additional context
Add any other context about the problem here.
I put some error logs below, hope them can help:
The text was updated successfully, but these errors were encountered: