hundreds-terabyte-36933
09/11/2022, 3:20 PMhundreds-terabyte-36933
09/11/2022, 3:23 PMmy_web_app:
https:
hosts:
- <http://abc.com|abc.com>
- <http://123.com|123.com>
hundreds-terabyte-36933
09/11/2022, 3:23 PMhundreds-terabyte-36933
09/11/2022, 3:40 PMthousands-oyster-32502
09/12/2022, 3:16 AMmodern-piano-42327
09/12/2022, 5:14 AMdocker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher
Rancher Docker container is unable to start
Logs : -
INFO: Running k3s server --cluster-init --cluster-reset
2022/09/12 05:05:08 [INFO] Rancher version v2.6.8 (f650ce839) is starting
2022/09/12 05:05:08 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2022/09/12 05:05:08 [INFO] Listening on /tmp/log.sock
2022/09/12 05:05:08 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:10 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:12 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:14 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:16 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:18 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:20 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:28 [INFO] Running in single server mode, will not peer connections
2022/09/12 05:05:28 [INFO] Applying CRD <http://features.management.cattle.io|features.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://navlinks.ui.cattle.io|navlinks.ui.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://clusters.management.cattle.io|clusters.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://apiservices.management.cattle.io|apiservices.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://clusterregistrationtokens.management.cattle.io|clusterregistrationtokens.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://settings.management.cattle.io|settings.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://preferences.management.cattle.io|preferences.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://features.management.cattle.io|features.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://clusterrepos.catalog.cattle.io|clusterrepos.catalog.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://operations.catalog.cattle.io|operations.catalog.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://apps.catalog.cattle.io|apps.catalog.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://fleetworkspaces.management.cattle.io|fleetworkspaces.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://managedcharts.management.cattle.io|managedcharts.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://clusters.provisioning.cattle.io|clusters.provisioning.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://clusters.provisioning.cattle.io|clusters.provisioning.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://rkeclusters.rke.cattle.io|rkeclusters.rke.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://rkecontrolplanes.rke.cattle.io|rkecontrolplanes.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://rkebootstraps.rke.cattle.io|rkebootstraps.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://rkebootstraptemplates.rke.cattle.io|rkebootstraptemplates.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://rkecontrolplanes.rke.cattle.io|rkecontrolplanes.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://custommachines.rke.cattle.io|custommachines.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://etcdsnapshots.rke.cattle.io|etcdsnapshots.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://clusters.cluster.x-k8s.io|clusters.cluster.x-k8s.io>
2022/09/12 05:05:30 [FATAL] k3s exited with: exit status 1
gorgeous-army-49867
09/12/2022, 7:41 AMerror during connect: Get "<http://localhost:2375/v1.24/containers/json>": dial tcp [::1]:2375: connectex: No connection could be made because the target machine actively refused it.
looking at logs and diffing between two machines i see this:
time="2022-09-12T07:01:32.085265700Z" level=info msg="Loading containers: start."
time="2022-09-12T07:01:32.143184300Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
time="2022-09-12T07:01:32.171789200Z" level=info msg="Loading containers: done."
time="2022-09-12T07:01:32.210623800Z" level=info msg="Docker daemon" commit=f756502055d2e36a84f2068e6620bea5ecf09058 graphdriver(s)=overlay2 version=20.10.16
time="2022-09-12T07:01:32.211010500Z" level=info msg="Daemon has completed initialization"
time="2022-09-12T07:01:32.240380700Z" level=info msg="API listen on /mnt/wsl/rancher-desktop/run/docker.sock"
time="2022-09-12T07:01:32.243100200Z" level=info msg="API listen on /var/run/docker.sock"
time="2022-09-12T07:01:47.099732600Z" level=error msg="(*service).Write failed" error="rpc error: code = Unavailable desc = ref moby/1/manifest-sha256:c2280d2f5f56cf9c9a01bb64b2db4651e35efd6d62a54dcfc12049fe6449c5e4 locked for 248.3627ms (since 2022-09-12 07:01:46.8005976 +0000 UTC m=+14.892781301): unavailable" expected="sha256:c2280d2f5f56cf9c9a01bb64b2db4651e35efd6d62a54dcfc12049fe6449c5e4" ref="manifest-sha256:c2280d2f5f56cf9c9a01bb64b2db4651e35efd6d62a54dcfc12049fe6449c5e4" total=526
time="2022-09-12T07:01:47.610257200Z" level=error msg="(*service).Write failed" error="rpc error: code = Unavailable desc = ref moby/1/manifest-sha256:c2280d2f5f56cf9c9a01bb64b2db4651e35efd6d62a54dcfc12049fe6449c5e4 locked for 721.2654ms (since 2022-09-12 07:01:46.8005976 +0000 UTC m=+14.892781301): unavailable" expected="sha256:c2280d2f5f56cf9c9a01bb64b2db4651e35efd6d62a54dcfc12049fe6449c5e4" ref="manifest-sha256:c2280d2f5f56cf9c9a01bb64b2db4651e35efd6d62a54dcfc12049fe6449c5e4" total=526
alert-fireman-21958
09/12/2022, 9:00 AMrefined-agent-67029
09/12/2022, 10:52 AMsalmon-carpenter-62625
09/12/2022, 12:14 PMjolly-area-75887
09/12/2022, 12:39 PMkubectl
I get this error
kubectl get ns --kubeconfig=rancher-project-admin.yaml
Error from server (Forbidden): namespaces is forbidden: User "u-xxxxxx" cannot list resource "namespaces" in API group "" at the cluster scope
brash-planet-10109
09/12/2022, 2:11 PMeager-refrigerator-66976
09/12/2022, 2:22 PMkind-analyst-38351
09/12/2022, 2:43 PMdry-angle-26883
09/12/2022, 3:18 PMkind-analyst-38351
09/12/2022, 4:20 PMincalculable-school-7570
dazzling-computer-84464
09/12/2022, 7:25 PM{
"baseType": "error",
"code": "ServerError",
"message": "error getting tokens for user: u-wkdcbhe4uz selector: <http://authn.management.cattle.io/token-userId=u-wkdcbhe4uz|authn.management.cattle.io/token-userId=u-wkdcbhe4uz> err: the server was unable to return a response in the time allotted, but may still be processing the request (get <http://tokens.meta.k8s.io|tokens.meta.k8s.io>)",
"status": 500,
"type": "error"
}
After upgrading to 2.6.6, the api https://rancher.domain.com/v3/tokens or user account & api key page not working anymore. Does anyone know how to fix this issue?dazzling-computer-84464
09/12/2022, 7:26 PMproud-salesmen-12221
09/13/2022, 1:53 AM[vagrant@rke2-server1 ~]$ kubectl get pods -A -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system cloud-controller-manager-rke2-server1 1/1 Running 2 (174m ago) 3h14m 10.0.2.15 rke2-server1 <none> <none>
kube-system etcd-rke2-server1 1/1 Running 1 (175m ago) 3h14m 192.168.33.101 rke2-server1 <none> <none>
kube-system helm-install-rke2-canal-c48pq 0/1 Completed 0 3h14m 10.0.2.15 rke2-server1 <none> <none>
kube-system helm-install-rke2-coredns-znhbd 0/1 Completed 0 3h14m 10.0.2.15 rke2-server1 <none> <none>
kube-system helm-install-rke2-ingress-nginx-fbp8s 0/1 Completed 0 3h14m 10.42.0.4 rke2-server1 <none> <none>
kube-system helm-install-rke2-metrics-server-4kcj7 0/1 Completed 0 3h14m 10.42.0.2 rke2-server1 <none> <none>
kube-system kube-apiserver-rke2-server1 1/1 Running 1 (175m ago) 3h14m 192.168.33.101 rke2-server1 <none> <none>
kube-system kube-controller-manager-rke2-server1 1/1 Running 2 (174m ago) 3h14m 10.0.2.15 rke2-server1 <none> <none>
kube-system kube-proxy-rke2-agent1 1/1 Running 0 173m 10.0.2.15 rke2-agent1 <none> <none>
kube-system kube-proxy-rke2-agent2 1/1 Running 0 173m 10.0.2.15 rke2-agent2 <none> <none>
kube-system kube-proxy-rke2-server1 1/1 Running 1 (175m ago) 3h14m 192.168.33.101 rke2-server1 <none> <none>
kube-system kube-scheduler-rke2-server1 1/1 Running 1 (175m ago) 3h14m 192.168.33.101 rke2-server1 <none> <none>
kube-system rke2-canal-m8vb6 2/2 Running 2 (175m ago) 3h14m 10.0.2.15 rke2-server1 <none> <none>
kube-system rke2-canal-ptnk8 0/2 CrashLoopBackOff 110 (87s ago) 3h10m 10.0.2.15 rke2-agent2 <none> <none>
kube-system rke2-canal-rmnv6 0/2 CrashLoopBackOff 110 (2m2s ago) 3h13m 10.0.2.15 rke2-agent1 <none> <none>
kube-system rke2-coredns-rke2-coredns-76cb76d66-mkv2c 1/1 Running 1 (175m ago) 3h14m 10.42.0.12 rke2-server1 <none> <none>
kube-system rke2-coredns-rke2-coredns-76cb76d66-t569h 0/1 ContainerCreating 0 3h13m <none> rke2-agent1 <none> <none>
kube-system rke2-coredns-rke2-coredns-autoscaler-58867f8fc5-8n589 1/1 Running 1 (175m ago) 3h14m 10.42.0.11 rke2-server1 <none> <none>
kube-system rke2-ingress-nginx-controller-c8vmd 0/1 ContainerCreating 0 3h9m <none> rke2-agent2 <none> <none>
kube-system rke2-ingress-nginx-controller-n9st4 1/1 Running 1 (175m ago) 3h14m 10.42.0.13 rke2-server1 <none> <none>
kube-system rke2-ingress-nginx-controller-rdml6 0/1 ContainerCreating 0 3h12m <none> rke2-agent1 <none> <none>
kube-system rke2-metrics-server-6979d95f95-4z57b 1/1 Running 1 (175m ago) 3h14m 10.42.0.10 rke2-server1 <none> <none>
flaky-shampoo-86024
09/13/2022, 3:14 AMstrong-painting-96413
09/13/2022, 3:25 AMfresh-king-12269
09/13/2022, 5:50 AMechoing-ability-7881
09/13/2022, 8:04 AMgorgeous-minister-309
09/13/2022, 8:04 AMretrieve_connection_info
function. The call to /v3/connect/agent
is failing with a 401 Unauthorized error.
The rancher server is accessible from the virtual machine. The script is called without any parameters but includes some references to my rancher instance : CATTLE_AGENT_BINARY_BASE_URL
, CATTLE_SERVER
, CATTLE_TOKEN
. I don't understand why this is failing.
Any idea?echoing-ability-7881
09/13/2022, 8:05 AMsome-addition-13540
09/13/2022, 8:21 AMpowerful-notebook-71999
09/13/2022, 12:36 PMbillions-honey-62634
09/13/2022, 10:22 PMkind: PersistentVolume
apiVersion: v1
metadata:
name: hostpath-pv
spec:
capacity:
storage: 1Gi
accessModes:
- ReadWriteOnce
reclaimPolicy:
- Recycle
hostPath:
path: "/data"
blue-tomato-62407
09/14/2022, 1:17 AM