Hello i rebooted my physical server with the rancher gui con rancher-users #general

Title

wonderful-judge-81095

05/11/2023, 6:41 PM

Hello, i rebooted my physical server with the rancher gui container and now port 8443 is not running on my server and the gui keep restarting over and over. rancher/rancher-agent:v2.3.1 "run.sh --server https://192.168.29.54:8443 --token cvvcj9fv68657ftb5c8qnmdlb5sh7tnlrgkx8bhbns42qbxrxj226 --ca-checksum cb 084998bd1cbcfa772bc513a3d7be868b87fec0da954c1d788995072212424 --no-register --only-write-certs" Any idea's on how to get this up and running? The original install of the container from a fresh install was docker run -d --restart=unless-stopped -p 8080:80 -p 8443:443 --privileged rancher/rancher:v2.3.1, this worked fine until the reboot and now port 8443 is not up.

creamy-pencil-82913

05/11/2023, 6:45 PM

Rancher 2.3 has been out of support since 2020

wonderful-judge-81095

05/11/2023, 6:51 PM

The environment is going away in a few months so I just need to keep it going a little longer

just noticed after my docker stop and reboot, the rancher/rancher container disappeared . In /var/lib/docker/containers it is missing. Does that mean a full reinstall and rebuild of the cluster would be required or can i just run docker run -d --restart=unless-stopped -p 8080:80 -p 8443:443 --privileged rancher/rancher:v2.3.1 again? Currently the cluster is up and running fine

creamy-pencil-82913

05/11/2023, 9:24 PM

rancher/rancher is just the Rancher Manager and its embedded local cluster. If you have downstream clusters, they would not be affected by anything going on with that standalone Docker container being down.

and fwiw, the rancher/rancher docker image isn’t supported for production use, it’s just for dev/poc

wonderful-judge-81095

05/11/2023, 9:46 PM

Thanks, If I understand correct, I should be able to reinstall rancher/rancher without impacting the current running cluster but I assume I wont be able to connect to it anymore if I run docker run -d --restart=unless-stopped -p 8080:80 -p 8443:443 --privileged rancher/rancher:v2.3.1 again?

this was all installed years ago with people that have left the company, i'm just inheriting the mess

i spent a full week getting the cluster up and running, i guess im a little shy in installing rancher/rancher again and breaking someting

creamy-pencil-82913

05/11/2023, 9:48 PM

I”m guessing the downstream cluster is also ancient?

wonderful-judge-81095

05/11/2023, 9:48 PM

i rebuit it all wtih 2.3.1 from scratch but the data was still on the centos so i just lost 5 days out of th 30 on disk

the volumes were fine

on each server i did the removal of all rancher, then installed rancher/rancher gui and then added rancher etc/controller and workloads back to those physical servers

all was great until i reboot the rancher/rancher server and lost the rancher/rancher container for some reason

basically, i rebuilt the rancher cluster from 2.3.1 which is was prior and removed prior rancher software on my physical servers. Then added new nodes to the cluster in rancher. Prior data on volumes were still there. So its an all new 2.3.1 rancher cluster without a running rancher/rancher gui to configure it anymore

poking around, i did a ps -a and found a rancher/rancher version that was different than my initial install but its up now. I see the cluster. the only error now is "CatalogTemplate.management.cattle.io "cattle-global-data/system-library-rancher-monitoring" not found"

which might be why i see "Monitoring API is not ready" at the cluster level, not global level

4 Views

#general Join Slack