https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
f
Logs of my docker container
Copy code
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2024/10/07 17:00:34 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
2024/10/07 17:00:38 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
202
2024/10/07 17:00:38 [ERROR] error syncing 'server-url': handler apiservice-settings: secrets "tls-rancher-internal-ca" not found, requeuing
202
p
For the docker command, did you use it on a different server than the rke2 node?
f
No, I did it in the same system where my RKE2 is present
I used same EC2 machine for both master and salves.
p
Yeah so i think the docker rancher cannot listen to the http prots because rke2 already occupy them
f
How can i change port for docker
p
sudo docker run --privileged -d --restart=unless-stopped -p 8080:80 -p 8443:443 rancher/rancher
basically edit port mapping
f
Thanks man, saved my life
Hi, I want to access Rancher through
Copy code
helm install rancher rancher-stable/rancher  --namespace cattle-system  --set hostname=<domain name>  --set bootstrapPassword=admin
command.

I have one domain attached to it.
Copy code
root@ip-172-31-29-88:/etc# kubectl get ingress -A
NAMESPACE       NAME      CLASS   HOSTS                        ADDRESS        PORTS     AGE
cattle-system   rancher   nginx   domain_name    172.31.29.88   80, 443   17h
When i created one ALB to point out it to the instance with ports 80, 443. But when i try to access it i am getting 404 Not found error. How can we change the port in the helm command
p
This i dont think you can change
f
How can i make it to work
p
what are the install logs for the help operation
f
sorry, I didn't understand. what do you mean by help operation?
p
helm*
sorry
f
Copy code
these are the error logs of the rancher pod

root@ip-172-31-29-88:/etc# kubectl logs rancher-6d49f86545-4x45t -n cattle-system | grep ERROR
2024/10/07 16:51:38 [ERROR] Failed to connect to peer <wss://10.42.0.23/v3/connect> [local ID=10.42.0.41]: websocket: bad handshake
2024/10/07 16:51:38 [ERROR] Failed to connect to peer <wss://10.42.0.24/v3/connect> [local ID=10.42.0.41]: websocket: bad handshake
2024/10/07 16:51:43 [ERROR] Failed to connect to peer <wss://10.42.0.23/v3/connect> [local ID=10.42.0.41]: websocket: bad handshake
2024/10/07 16:51:43 [ERROR] Failed to connect to peer <wss://10.42.0.24/v3/connect> [local ID=10.42.0.41]: websocket: bad handshake
2024/10/07 16:51:48 [ERROR] Failed to connect to peer <wss://10.42.0.24/v3/connect> [local ID=10.42.0.41]: dial tcp 10.42.0.24:443: connect: connection refused
2024/10/07 16:51:48 [ERROR] Failed to handle tunnel request from remote address 10.42.0.23:48302: response 400: cluster not found
2024/10/07 16:51:48 [ERROR] Failed to connect to peer <wss://10.42.0.23/v3/connect> [local ID=10.42.0.41]: websocket: bad handshake
2024/10/07 16:52:05 [ERROR] Failed to handle tunnel request from remote address 10.42.0.42:42940: response 400: cluster not found
2024/10/07 16:52:10 [ERROR] Failed to serve peer connection 10.42.0.40: websocket: close 1006 (abnormal closure): unexpected EOF
2024/10/07 23:51:56 [ERROR] error syncing 'rancher-rke2-charts': handler helm-clusterrepo-ensure: ensure failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-rke2-charts/675f1b63a0a83905972dcab2794479ed599a6f41b86cd6193d69472d0fa889c9 fetch origin -- 197946c0a9114bb5424cb61c38823a6e0c7fad1e error: exit status 128, detail: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
2024/10/07 23:51:59 [ERROR] error syncing 'rancher-rke2-charts': handler helm-clusterrepo-ensure: ensure failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-rke2-charts/675f1b63a0a83905972dcab2794479ed599a6f41b86cd6193d69472d0fa889c9 fetch origin -- 197946c0a9114bb5424cb61c38823a6e0c7fad1e error: exit status 128, detail: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
2024/10/07 23:52:02 [ERROR] error syncing 'rancher-rke2-charts': handler helm-clusterrepo-ensure: ensure failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-rke2-charts/675f1b63a0a83905972dcab2794479ed599a6f41b86cd6193d69472d0fa889c9 fetch origin -- 197946c0a9114bb5424cb61c38823a6e0c7fad1e error: exit status 128, detail: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
2024/10/07 23:52:05 [ERROR] error syncing 'rancher-rke2-charts': handler helm-clusterrepo-ensure: ensure failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-rke2-charts/675f1b63a0a83905972dcab2794479ed599a6f41b86cd6193d69472d0fa889c9 fetch origin -- 197946c0a9114bb5424cb61c38823a6e0c7fad1e error: exit status 128, detail: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
2024/10/08 01:51:58 [ERROR] error syncing 'rancher-partner-charts': handler helm-clusterrepo-ensure: ensure failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-partner-charts/8f17acdce9bffd6e05a58a3798840e408c4ea71783381ecd2e9af30baad65974 fetch origin -- 87b254a3a2b02da351f601ce85ba042a3fa78e56 error: exit status 128, detail: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
I didn't have the install logs of helm
p
if you remove the grep errors what are the 20 latest lines
f
Copy code
2024/10/07 23:52:05 [ERROR] error syncing 'rancher-rke2-charts': handler helm-clusterrepo-ensure: ensure failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-rke2-charts/675f1b63a0a83905972dcab2794479ed599a6f41b86cd6193d69472d0fa889c9 fetch origin -- 197946c0a9114bb5424cb61c38823a6e0c7fad1e error: exit status 128, detail: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
fatal: the remote end hung up unexpectedly
, requeuing
2024/10/08 01:51:58 [ERROR] error syncing 'rancher-partner-charts': handler helm-clusterrepo-ensure: ensure failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-partner-charts/8f17acdce9bffd6e05a58a3798840e408c4ea71783381ecd2e9af30baad65974 fetch origin -- 87b254a3a2b02da351f601ce85ba042a3fa78e56 error: exit status 128, detail: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
fatal: the remote end hung up unexpectedly
, requeuing
W1008 02:51:37.962880      39 warnings.go:70] v1 ComponentStatus is deprecated in v1.19+
2024/10/08 02:51:38 [INFO] Updating TLS secret for cattle-system/tls-rancher-internal (count: 4): map[<http://field.cattle.io/projectId:local:p-npdmp|field.cattle.io/projectId:local:p-npdmp> <http://listener.cattle.io/cn-10.42.0.24:10.42.0.24|listener.cattle.io/cn-10.42.0.24:10.42.0.24> <http://listener.cattle.io/cn-10.42.0.25:10.42.0.25|listener.cattle.io/cn-10.42.0.25:10.42.0.25> <http://listener.cattle.io/cn-10.43.147.179:10.43.147.179|listener.cattle.io/cn-10.43.147.179:10.43.147.179> <http://listener.cattle.io/fingerprint:SHA1=5CF28FF59E11D4F8082313D18B2E3CDB70C6A9C3]|listener.cattle.io/fingerprint:SHA1=5CF28FF59E11D4F8082313D18B2E3CDB70C6A9C3]>
2024/10/08 02:51:38 [INFO] Updating TLS secret for cattle-system/serving-cert (count: 10): map[<http://field.cattle.io/projectId:local:p-npdmp|field.cattle.io/projectId:local:p-npdmp> <http://listener.cattle.io/cn-10.42.0.23:10.42.0.23|listener.cattle.io/cn-10.42.0.23:10.42.0.23> <http://listener.cattle.io/cn-10.42.0.24:10.42.0.24|listener.cattle.io/cn-10.42.0.24:10.42.0.24> <http://listener.cattle.io/cn-10.42.0.25:10.42.0.25|listener.cattle.io/cn-10.42.0.25:10.42.0.25> <http://listener.cattle.io/cn-10.42.0.40:10.42.0.40|listener.cattle.io/cn-10.42.0.40:10.42.0.40> <http://listener.cattle.io/cn-10.42.0.41:10.42.0.41|listener.cattle.io/cn-10.42.0.41:10.42.0.41> <http://listener.cattle.io/cn-10.42.0.42:10.42.0.42|listener.cattle.io/cn-10.42.0.42:10.42.0.42> <http://listener.cattle.io/cn-127.0.0.1:127.0.0.1|listener.cattle.io/cn-127.0.0.1:127.0.0.1> <http://listener.cattle.io/cn-localhost:localhost|listener.cattle.io/cn-localhost:localhost> <http://listener.cattle.io/cn-rancher.cattle-system:rancher.cattle-system|listener.cattle.io/cn-rancher.cattle-system:rancher.cattle-system> <http://listener.cattle.io/fingerprint:SHA1=5B5BE2B310FC9E9B42B9140CDC83931D2E1AC0E8]|listener.cattle.io/fingerprint:SHA1=5B5BE2B310FC9E9B42B9140CDC83931D2E1AC0E8]>
W1008 02:51:39.309791      39 warnings.go:70] v1 ComponentStatus is deprecated in v1.19+
p
huh
if you check the logs for rke2-ingress-controller pod, do you see the 404 ?
Because that 404 i think is sent out by ALB and not RKE2
is this good?
f
Yes, they are running fine
Copy code
kubectl logs -n kube-system                       rke2-ingress-nginx-controller-4g4zv
W1007 15:53:22.400463       7 controller.go:1213] Service "cattle-system/rancher" does not have any active Endpoint.
W1007 15:53:22.400463       7 controller.go:1213] Service "cattle-system/rancher" does not have any active Endpoint.
You suspect it as a port issue when i try to install using helm, when i add slave node, do you think my issue is gone
Hi, for installation of Rancher does load balancer is directly created by helm in AWS or we need to create them
31 Views
Open in Slack
PreviousNext
Powered by