This message was deleted.
# k3sa
adamant-kite-43734
10/08/2022, 11:50 AMThis message was deleted.
c
cool-petabyte-32540
10/08/2022, 4:17 PMHow did you try to upgrade the rancher server from v2.5.7 to v2.6.8?
r
red-boots-23091
10/08/2022, 4:22 PMThank you for your reply. I followed this path http://docs.ranchermanager.rancher.io//getting-started/installation-and-upgrade/other-installation-methods/rancher-on-a-single-node-with-docker/upgrade-docker-installed-rancher
c
cool-petabyte-32540
10/08/2022, 5:57 PMFirst try upgrading to v2.6.3.
r
red-boots-23091
10/08/2022, 6:00 PMI did I get the same results no matter what version I upgrade too
c
cool-petabyte-32540
10/08/2022, 6:08 PMTry this workaround
https://github.com/rancher/rancher/issues/29223#issuecomment-969901491
r
red-boots-23091
10/08/2022, 6:17 PMThank you for the suggestion. I have also tried this. Rancher comes up but kubectl still doesnt work and I get connection refused in the logs. The logs I posted earlier did not have the grub edits. I will post logs from after this grub update
red-boots-23091
10/08/2022, 7:53 PM2022/10/08 19:42:24 [INFO] Rancher version v2.6.8 (f650ce839) is starting2022/10/08 19:42:24 [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/10/08 19:42:24 [INFO] Listening on /tmp/log.sock2022/10/08 19:42:24 [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 refused2022/10/08 19:46:01 [INFO] Running in single server mode, will not peer connections2022/10/08 19:46:08 [INFO] Applying CRD <http://features.management.cattle.io|features.management.cattle.io>2022/10/08 19:46:59 [FATAL] k3s exited with: exit status 1red-boots-23091
10/08/2022, 8:12 PMthis was my docker run command, for reference
docker run -d --volumes-from rancher-data --restart=unless-stopped -p 9090:80 -p 9091:443 --privileged -v /opt/rancher:/var/lib/rancher --name=rancher_docker_server rancher/rancher:v2.6.8c
cool-petabyte-32540
10/09/2022, 1:02 AMFollowing issue seems same. Try upgrading to 2.7.0-rc3.
If it doesn't work, not sure how this issue can be solved.
https://github.com/rancher/rancher/issues/36238
r
red-boots-23091
10/09/2022, 7:39 AMThank you for advice I tried 2.7- head yesterday after seeing this github issue. However got lots of etcd errors. I will try this version thank you for your suggestions
c
cool-petabyte-32540
10/09/2022, 8:40 AMTry with rc3 version
cool-petabyte-32540
10/09/2022, 9:18 AMv2.7-head is not stable
r
red-boots-23091
10/09/2022, 10:40 AMShould I upgrade view versions or straight from 2.5.7?
c
cool-petabyte-32540
10/09/2022, 11:00 AMStraight from 2.5.7
👍 1
r
red-boots-23091
10/11/2022, 1:26 PMHi V2.7-rc3 also did not work, however I managed to get v2.5.7 working by deleting the
Copy code
dynamic-cert.jsonGRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0"red-boots-23091
10/11/2022, 1:26 PMhowever its not stable
c
cool-petabyte-32540
10/11/2022, 1:27 PMOkay
r
red-boots-23091
10/11/2022, 1:28 PMi will pastebin logs maybe you will see something else that might help further
red-boots-23091
10/11/2022, 1:28 PMthank you for your help so far
red-boots-23091
10/11/2022, 2:09 PM3 Views