eager-potato-98069
01/04/2023, 7:47 AMeager-potato-98069
01/04/2023, 7:48 AMeager-potato-98069
01/04/2023, 7:48 AMagreeable-oil-87482
01/04/2023, 9:34 AMthankful-balloon-877
01/04/2023, 9:56 AMloud-nest-3266
01/04/2023, 10:25 AMearly-rain-36108
01/04/2023, 10:45 AMchilly-intern-2653
01/04/2023, 7:58 PMmagnificent-jackal-25711
01/04/2023, 8:27 PMmysterious-minister-97036
01/05/2023, 8:02 AMearly-lifeguard-63817
01/05/2023, 4:33 PMcalm-oil-38842
01/05/2023, 5:54 PMworried-nest-47450
01/06/2023, 6:01 AMkubectl get nodes
, the node's status is shown as Ready
, so I am confusedmysterious-hospital-56910
01/06/2023, 2:18 PMbored-laptop-94633
01/06/2023, 9:33 PMsquare-rose-18388
01/06/2023, 9:41 PMfaint-garden-16510
01/06/2023, 10:06 PMsome-lawyer-90399
01/07/2023, 11:02 PMhelpful-dress-48416
01/08/2023, 10:47 AMhelpful-dress-48416
01/08/2023, 10:47 AMhelpful-dress-48416
01/08/2023, 10:47 AMbumpy-accountant-48077
01/08/2023, 1:23 PMdry-businessperson-74633
01/08/2023, 4:01 PMdry-businessperson-74633
01/08/2023, 4:02 PMhundreds-jewelry-18968
01/09/2023, 1:10 AMYou must be logged in to the server (Unauthorized)
Checking the master node, the k3s service Im seeing this:
● k3s.service - Lightweight Kubernetes
Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2023-01-09 00:57:40 GMT; 26s ago
Docs: <https://k3s.io>
Process: 29663 ExecStartPre=/bin/sh -xc ! /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service (code=exited, status=0/SUCCESS)
Process: 29665 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
Process: 29666 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
Main PID: 29667 (k3s-server)
Tasks: 105
Memory: 713.5M
CPU: 55.998s
CGroup: /system.slice/k3s.service
├─27643 /var/lib/rancher/k3s/data/73e12683e3eb1c52a6370763bda6bb977c304a3b6cda6e5c7656f45f3725e7dd/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id 866ca3db8ed3>
├─27988 /var/lib/rancher/k3s/data/73e12683e3eb1c52a6370763bda6bb977c304a3b6cda6e5c7656f45f3725e7dd/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id 699af3f5d3c1>
├─28196 /var/lib/rancher/k3s/data/73e12683e3eb1c52a6370763bda6bb977c304a3b6cda6e5c7656f45f3725e7dd/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id ac9ec12775e6>
├─28317 /var/lib/rancher/k3s/data/73e12683e3eb1c52a6370763bda6bb977c304a3b6cda6e5c7656f45f3725e7dd/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id b345387839df>
├─28535 /var/lib/rancher/k3s/data/73e12683e3eb1c52a6370763bda6bb977c304a3b6cda6e5c7656f45f3725e7dd/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id 880445942eb9>
├─29667 /usr/local/bin/k3s server
└─29683 containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/ra>
Jan 09 00:58:01 facio k3s[29667]: I0109 00:58:01.010177 29667 ttl_controller.go:121] Starting TTL controller
Jan 09 00:58:01 facio k3s[29667]: I0109 00:58:01.010203 29667 shared_informer.go:240] Waiting for caches to sync for TTL
Jan 09 00:58:01 facio k3s[29667]: I0109 00:58:01.022756 29667 node_ipam_controller.go:91] Sending events to api server.
Jan 09 00:58:01 facio k3s[29667]: E0109 00:58:01.441328 29667 authentication.go:63] "Unable to authenticate the request" err="[x509: certificate has expired or is not yet v>
Jan 09 00:58:04 facio k3s[29667]: E0109 00:58:04.547721 29667 authentication.go:63] "Unable to authenticate the request" err="[x509: certificate has expired or is not yet v>
Jan 09 00:58:04 facio k3s[29667]: E0109 00:58:04.548614 29667 authentication.go:63] "Unable to authenticate the request" err="[x509: certificate has expired or is not yet v>
Jan 09 00:58:04 facio k3s[29667]: E0109 00:58:04.548867 29667 authentication.go:63] "Unable to authenticate the request" err="[x509: certificate has expired or is not yet v>
I saw this error before but I reinstall the cluster. I prefer not to do it again to avoid loosing data. Anyone knows how I can fix:
"Unable to authenticate the request" err="[x509: certificate has expired or is not yet v>
(edited)
[1:09 AM] I havent changed anything on the machine running K3S at allhundreds-jewelry-18968
01/09/2023, 1:22 AMJan 09 01:18:01 facio k3s[29667]: E0109 01:18:01.542615 29667 authentication.go:63] "Unable to authenticate the request" err="[x509: certificate has expired or is not yet valid: current time 2023-01-09T01:18:01Z is after 2023-01-08T22:37:57Z, verifying certificate SN=2555825581207100645, SKID=,AKID=8F:E9:C8:2E:7F:91:B7:01:BC:7A:48:DD:77:8C:6A:EF:92:DA:E5:58 failed: x509: certificate has expired or is not yet valid: current time 2023-01-09T01:18:01Z is after 2023-01-08T22:37:57Z]"
can’t understand how this happened current time 2023-01-09T01:18:01Z is after 2023-01-08T22:37:57Z
bored-planet-1228
01/09/2023, 2:56 AM> nerdctl pull alpine
INFO[0000] trying next host error="failed to do request: Head \"<https://registry-1.docker.io/v2/library/alpine/manifests/latest>\": proxyconnect tcp: dial tcp 127.0.0.1:3128: connect: connection refused" host=<http://registry-1.docker.io|registry-1.docker.io>
ERRO[0000] server "<http://docker.io|docker.io>" does not seem to support HTTPS error="failed to resolve reference \"<http://docker.io/library/alpine:latest\|docker.io/library/alpine:latest\>": failed to do request: Head \"<https://registry-1.docker.io/v2/library/alpine/manifests/latest>\": proxyconnect tcp: dial tcp 127.0.0.1:3128: connect: connection refused"
INFO[0000] Hint: you may want to try --insecure-registry to allow plain HTTP (if you are in a trusted network)
FATA[0000] failed to resolve reference "<http://docker.io/library/alpine:latest|docker.io/library/alpine:latest>": failed to do request: Head "<https://registry-1.docker.io/v2/library/alpine/manifests/latest>": proxyconnect tcp: dial tcp 127.0.0.1:3128: connect: connection refused
Error: exit status 1
bored-planet-1228
01/09/2023, 2:57 AMwitty-tiger-89786
01/09/2023, 8:16 AMadorable-exabyte-35533
01/09/2023, 10:02 AM