Closed mr-onion-2 closed 2 years ago
I ended up rebuilding. If it happens again I'll re-open
Re-opening since this has occurred again.
The cluster had been working flawlessly since October. This morning I drained and rebooted the master node and it failed to start back up. Same errors in the log as in the original comment. Automatic upgrades were disabled this time, so nothing should have changed :\
Closing this again as I believe it was caused by user config :)
I run K3OS on a Pi cluster. I use an internal NTP server but the master node looks to have failed to sync the time successfully. Since Pi's do not have a Real Time Clock, the date was 1970-01-01. I'm guessing this was the reason for the bearer token errors.
k3os version v0.19.15-k3s2r0 5.4.51-v8+ #1333 SMP PREEMPT Mon Aug 10 16:58:35 BST 2020 aarch64
Hi My cluster has been working flawlessly until about 2am this morning. I could be wrong but I am guessing that it tried to perform auto-upgrade, and now it will not start. The logs point to an invalid bearer token.
k3s --debug server produces the following.
Not sure if this is a problem but k3s check-config shows 6 errors as per below.
Please let me know if I can provide any further information. I did not want to label this as a bug since I have no evidence of that and cannot easily reproduce (for the moment at least)