Look for the next rodeo; they’re really good.

The most important part of the log comes from the rancher-agent:

time="2022-08-19T07:03:38Z" level=info msg="Connecting to <wss://rancher.gandalf.mordor.net/v3/connect> with token starting with 4sfxz9dk54w2hp9xv729k8tbgnf"
time="2022-08-19T07:03:38Z" level=info msg="Connecting to proxy" url="<wss://rancher.gandalf.mordor.net/v3/connect>"
time="2022-08-19T07:03:48Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp 20.42.142.242:443: i/o timeout"
time="2022-08-19T07:03:48Z" level=error msg="Remotedialer proxy error" error="dial tcp 20.42.142.242:443: i/o timeout"
time="2022-08-19T07:03:50Z" level=warning msg="Error while getting agent config: Get \"<https://rancher.gandalf.mordor.net/v3/connect/config>\": dial tcp 20.42.142.242:443: i/o timeout"
time="2022-08-19T07:03:58Z" level=info msg="Connecting to <wss://rancher.gandalf.mordor.net/v3/connect> with token starting with 4sfxz9dk54w2hp9xv729k8tbgnf"
time="2022-08-19T07:03:58Z" level=info msg="Connecting to proxy" url="<wss://rancher.gandalf.mordor.net/v3/connect>"
time="2022-08-19T07:04:08Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp 20.42.142.242:443: i/o timeout"
time="2022-08-19T07:04:08Z" level=error msg="Remotedialer proxy error" error="dial tcp 20.42.142.242:443: i/o timeout"
time="2022-08-19T07:04:18Z" level=info msg="Connecting to <wss://rancher.gandalf.mordor.net/v3/connect> with token starting with 4sfxz9dk54w2hp9xv729k8tbgnf"
time="2022-08-19T07:04:18Z" level=info msg="Connecting to proxy" url="<wss://rancher.gandalf.mordor.net/v3/connect>"
time="2022-08-19T07:04:25Z" level=warning msg="Error while getting agent config: Get \"<https://rancher.gandalf.mordor.net/v3/connect/config>\": dial tcp 20.42.142.242:443: i/o timeout"
time="2022-08-19T07:04:28Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp 20.42.142.242:443: i/o timeout"
time="2022-08-19T07:04:28Z" level=error msg="Remotedialer proxy error" error="dial tcp 20.42.142.242:443: i/o timeout"
time="2022-08-19T07:04:38Z" level=info msg="Connecting to <wss://rancher.gandalf.mordor.net/v3/connect> with token starting with 4sfxz9dk54w2hp9xv729k8tbgnf"
time="2022-08-19T07:04:38Z" level=info msg="Connecting to proxy" url="<wss://rancher.gandalf.mordor.net/v3/connect>"
time="2022-08-19T07:04:48Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp 20.42.142.242:443: i/o timeout"
time="2022-08-19T07:04:48Z" level=error msg="Remotedialer proxy error" error="dial tcp 20.42.142.242:443: i/o timeout"
time="2022-08-19T07:04:58Z" level=info msg="Connecting to <wss://rancher.gandalf.mordor.net/v3/connect> with token starting with 4sfxz9dk54w2hp9xv729k8tbgnf"
time="2022-08-19T07:04:58Z" level=info msg="Connecting to proxy" url="<wss://rancher.gandalf.mordor.net/v3/connect>"
time="2022-08-19T07:05:00Z" level=warning msg="Error while getting agent config: Get \"<https://rancher.gandalf.mordor.net/v3/connect/config>\": dial tcp 20.42.142.242:443: i/o timeout"

👋 Hallo zusammen!

I am running rancher on a single node linux host (fedora 36) that I recently upgraded from fedora 32. Rancher is having a problem starting properly. I am trying to follow the troubleshooting guide (https://rancher.com/docs/rancher/v2.5/en/troubleshooting/dns/). I’m noticing that the coredns pod is not starting…

$ kubectl -n kube-system get pods -l k8s-app=kube-dns
NAME                       READY   STATUS             RESTARTS   AGE
coredns-685d6d555d-q9pn4   0/1     CrashLoopBackOff   4          2m40s

If I look at the pod description I see the events as follows:

Type     Reason          Age                From     Message
  ----     ------          ----               ----     -------
  Normal   SandboxChanged  62m (x2 over 62m)  kubelet  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled          62m                kubelet  Container image "rancher/mirrored-cluster-proportional-autoscaler:1.8.3" already present on machine
  Normal   Created         62m                kubelet  Created container autoscaler
  Normal   Started         62m                kubelet  Started container autoscaler
  Normal   SandboxChanged  52m (x2 over 52m)  kubelet  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled          52m                kubelet  Container image "rancher/mirrored-cluster-proportional-autoscaler:1.8.3" already present on machine
  Normal   Created         52m                kubelet  Created container autoscaler
  Normal   Started         52m                kubelet  Started container autoscaler
  Warning  Unhealthy       51m                kubelet  Readiness probe failed: Get "<http://10.42.0.17:8080/healthz>": dial tcp 10.42.0.17:8080: i/o timeout (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy       51m (x3 over 52m)  kubelet  Readiness probe failed: Get "<http://10.42.0.17:8080/healthz>": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Normal   SandboxChanged  37m (x2 over 37m)  kubelet  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled          37m                kubelet  Container image "rancher/mirrored-cluster-proportional-autoscaler:1.8.3" already present on machine
  Normal   Created         37m                kubelet  Created container autoscaler
  Normal   Started         37m                kubelet  Started container autoscaler
  Warning  Unhealthy       36m (x2 over 37m)  kubelet  Readiness probe failed: Get "<http://10.42.0.93:8080/healthz>": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Normal   SandboxChanged  22m (x2 over 22m)  kubelet  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled          22m                kubelet  Container image "rancher/mirrored-cluster-proportional-autoscaler:1.8.3" already present on machine
  Normal   Created         22m                kubelet  Created container autoscaler
  Normal   Started         22m                kubelet  Started container autoscaler
  Warning  Unhealthy       21m (x4 over 22m)  kubelet  Readiness probe failed: Get "<http://10.42.0.161:8080/healthz>": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

It seems to be failing the health check, but I’m not sure why

Hi! I just try to spin up a GitLab instance via Docker container on Rancher. However, I am hitting the problem that, after each restart of the Pod the data is completly reset. I use a StatefulSet which crates a Persistent Volume Claim on Longhorn. On Longhorn it also really creates this claim and puts data in it. However after a reastart of the Pod it does not use this data, but creats everything anew. The amount of data in Longhorn does not change, but I guess this is because this it it just overwrites everything. I think my error is that I translate the mount points of the GitLab image falsely into the UI fields offered by rancher. Following this guide (https://www.rancher.cn/how-to-run-gitlab-in-rancher-1/ and this documentation: https://docs.gitlab.com/ee/install/docker.html#set-up-the-volumes-location) I entered this: • gitlab-etc:/etc/gitlab • gitlab-opt:/var/opt/gitlab • gitlab-log:/var/log/gitlab into the mount point fields (see picture). What am I doing wrong?

I need to know how to install KIM

When using the Rancher HTTPS API, did anyone manage to connect via websocket to something? There's no documentation or examples but it should work

Office hours today?

Aloha

it started in a snap, and then it slowly became a problem . . .

thats a name I haven’t seen in a while 🙂

are you that Vic Bancroft?

Wow, @broad-ambulance-17822!!!

Yes, I am . . .

long time no see 😄

Last time we hung out was in some cubes in ALP

absolutely. btw I think the Aloha gave you away 😄

So, have you ever done k3s on bare metal ?

At least I know I finally found where the cool kids hang out !

there’s a #k3s channel too

When I try to install Rancher Server 2.6.6 on k3s > 1.24.0 it fails because the limit is set in the Helm Chart for that k3s version. However, if I install k3s <1.24.0, install Rancher Server 2.6.6, then upgrade the underlying k3s, I can use something > 1.24.0. How dangerous is this and does this suggest Rancher Server should always be upgraded prior to it’s underlying k3s cluster?

Got this working with the proper depricated graph endpoint. https://graph.microsoft.com The one at the bottom of this page is wrong https://rancher.com/docs/rancher/v2.6/en/admin-settings/authentication/azure-ad/

Has anyone tried to use multus cni on k3d?

Hi, I am facing issues to add a new node by following the steps at https://docs.rke2.io/install/quickstart/. rke2 version v1.23.9+rke2r1 (2d206eba8d0180351408dbed544c852b6b4fdd42) for both server and node node side: cat /etc/rancher/rke2/config.yaml server: https://190.190.190.83:9345 token: xxxx:😒erver:xxxxx erro log: iting to retrieve agent configuration; server is not ready: failed to retrieve configuration from server: https://127.0.0.1:6444/v1-rke2/config: 401 Unauthorized" Server side: The token above is from /var/lib/rancher/rke2/server/node-token Aug 21 16:49:01 tusdesign rke2[907]: time="2022-08-21T16:49:01+08:00" level=error msg="Failed to authenticate request from 190.190.190.82:49402: invalid username/password combination" ======================================== Was able to add another node

👋 Hi everyone! Hey is it possible to use rancher in one organization connected account to manage/create eks clusters in other connected accounts? Ive tried to do so, but the cluster never fully provisions in rancher. The EKS side of things looks okay.

Hello eveyone...i have a question about rancher-pushprox. what i am trying to do is to add a cusome label to all metrics which rancher-pushprox are scrapping.for other component that rancher pushprox is not responsible iam using metric relabeling which works find.but i have no such option in rancher-pushprox...is there any way to solve my requirment?

i need to add a label called cluster: centeralmonitoring

Hello, is there any rancher version which can support k8s version : 1.2

?