https://rancher.com/ logo
Join Slack
Powered by
Is the api for checking for upgrades down? From l...
# rancher-desktop
a
Is the api for checking for upgrades down? From logs:
Copy code
2025-03-17T12:33:07.615Z: UnhandledRejectionWarning: FetchError: invalid json response body at <https://desktop.version.rancher.io/v1/checkupgrade> reason: Unexpected token '<', "<html>
<h"... is not valid JSON
When I try to curl that endpoint or hit it in a browser, I’m getting a 502 Bad Gateway.
p
Thanks, that does look down; let me get that looked at.
a
Any updates here? This is preventing me from using dockerd on my Mac as I rely on rancher for that.
p
The infra guys are picking that up. But that sounds like a bug, in that the update endpoint being down shouldn't block you from using Rancher Desktop…
a
Rancher Desktop is throwing the error from my screenshot. It’s not starting up whatever services/etc. that allow me to use the docker cli on my Mac. I’m using dockerd (moby) as my container engine. When Rancher Desktop isn’t running, I can’t use docker cli on my Mac. This error appears to be preventing it from serving up that service.
p
That error seems to have to do with 
limactl
and not the update stuff. If you can get to the main window, please look at the logs to see if there are any relevant details (I usually start from 
background.log
); but I guess you already found the logs to notice the update failure?
a
The error I pasted was from background.log.
p
Right; are there more errors?
a
Copy code
2025-03-17T19:22:42.011Z: mainEvents settings-update: {"version":14,"containerEngine":{"name":"moby","allowedImages":{"enabled":false,"locked":false,"patterns":[]}},"kubernetes":{"version":"1.26.4","port":6443,"enabled":false,"options":{"traefik":true,"flannel":true},"ingress":{"localhostOnly":false}},"portForwarding":{"includeKubernetesServices":false},"images":{"showAll":true,"namespace":"<http://k8s.io|k8s.io>"},"diagnostics":{"showMuted":false,"mutedChecks":{}},"application":{"adminAccess":true,"debug":false,"pathManagementStrategy":"rcfiles","telemetry":{"enabled":false},"updater":{"enabled":false},"autoStart":true,"startInBackground":false,"hideNotificationIcon":false,"window":{"quitOnClose":false},"extensions":{"allowed":{"enabled":false,"list":[]},"installed":{}}},"virtualMachine":{"memoryInGB":8,"numberCPUs":4},"experimental":{"virtualMachine":{"type":"vz","useRosetta":false,"mount":{"type":"virtiofs","9p":{"securityModel":"none","protocolVersion":"9p2000.L","msizeInKB":128,"cacheMode":"mmap","msizeInKib":128}},"proxy":{"enabled":false,"address":"","password":"","port":3128,"username":"","noproxy":["0.0.0.0/8","10.0.0.0/8","127.0.0.0/8","169.254.0.0/16","172.16.0.0/12","192.168.0.0/16","224.0.0.0/4","240.0.0.0/4"]}},"containerEngine":{"webAssembly":{"enabled":false}},"kubernetes":{"options":{"spinkube":false}}},"WSL":{"integrations":{}},"containers":{"showAll":true,"namespace":"default"}}
2025-03-17T19:22:43.696Z: Kubernetes was unable to start: c [Error]: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> exited with code 1
    at ChildProcess.<anonymous> (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:2:185000|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:2:185000>)
    at ChildProcess.emit (node:events:519:28)
    at ChildProcess._handle.onexit (node:internal/child_process:294:12) {
  command: [
    '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl>',
    'start',
    '--tty=false',
    '0'
  ],
  stdout: '',
  stderr: 'time="2025-03-17T15:22:43-04:00" level=info msg="Using the existing instance \\"0\\""\n' +
    'time="2025-03-17T15:22:43-04:00" level=fatal msg="errors inspecting instance: [failed to get Info from \\"/Users/tim/Library/Application Support/rancher-desktop/lima/0/ha.sock\\": Get \\"<http://lima-hostagent/v1/info>\\": dial unix /Users/tim/Library/Application Support/rancher-desktop/lima/0/ha.sock: connect: connection refused]"\n',
  code: 1,
  [Symbol(child-process.command)]: '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> start --tty=false 0'
}
2025-03-17T19:22:52.029Z: mainEvents settings-update: {"version":14,"containerEngine":{"name":"moby","allowedImages":{"enabled":false,"locked":false,"patterns":[]}},"kubernetes":{"version":"1.26.4","port":6443,"enabled":false,"options":{"traefik":true,"flannel":true},"ingress":{"localhostOnly":false}},"portForwarding":{"includeKubernetesServices":false},"images":{"showAll":true,"namespace":"<http://k8s.io|k8s.io>"},"diagnostics":{"showMuted":false,"mutedChecks":{}},"application":{"adminAccess":true,"debug":false,"pathManagementStrategy":"rcfiles","telemetry":{"enabled":false},"updater":{"enabled":true},"autoStart":true,"startInBackground":false,"hideNotificationIcon":false,"window":{"quitOnClose":false},"extensions":{"allowed":{"enabled":false,"list":[]},"installed":{}}},"virtualMachine":{"memoryInGB":8,"numberCPUs":4},"experimental":{"virtualMachine":{"type":"vz","useRosetta":false,"mount":{"type":"virtiofs","9p":{"securityModel":"none","protocolVersion":"9p2000.L","msizeInKB":128,"cacheMode":"mmap","msizeInKib":128}},"proxy":{"enabled":false,"address":"","password":"","port":3128,"username":"","noproxy":["0.0.0.0/8","10.0.0.0/8","127.0.0.0/8","169.254.0.0/16","172.16.0.0/12","192.168.0.0/16","224.0.0.0/4","240.0.0.0/4"]}},"containerEngine":{"webAssembly":{"enabled":false}},"kubernetes":{"options":{"spinkube":false}}},"WSL":{"integrations":{}},"containers":{"showAll":true,"namespace":"default"}}
2025-03-17T19:22:52.418Z: UnhandledRejectionWarning: FetchError: invalid json response body at <https://desktop.version.rancher.io/v1/checkupgrade> reason: Unexpected token '<', "<html>
<h"... is not valid JSON
    at /Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/node_modules/node-fetch/lib/index.js:273:32|Desktop.app/Contents/Resources/app.asar/node_modules/node-fetch/lib/index.js:273:32>
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:102365|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:102365>
    at async Ui.checkForUpdates (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:101767|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:101767>)
    at async Ui.getLatestVersion (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:104301|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:104301>)
    at async MacUpdater.getUpdateInfoAndProvider (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/node_modules/electron-updater/out/AppUpdater.js:343:19|Desktop.app/Contents/Resources/app.asar/node_modules/electron-updater/out/AppUpdater.js:343:19>)
    at async MacUpdater.doCheckForUpdates (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/node_modules/electron-updater/out/AppUpdater.js:356:24|Desktop.app/Contents/Resources/app.asar/node_modules/electron-updater/out/AppUpdater.js:356:24>)
    at async es (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:108686|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:108686>) {
  type: 'invalid-json'
}
p
UnhandledRejectionWarning
means we did something asynchronously, and the error wasn't handled, so it just got dropped on the floor and ignored…
Ah, so the host agent is crashing or otherwise not responding: 
level=fatal msg="errors inspecting instance: [failed to get Info from \\"/Users/tim/Library/Application Support/rancher-desktop/lima/0/ha.sock\\": Get \\"<http://lima-hostagent/v1/info>\\": dial unix /Users/tim/Library/Application Support/rancher-desktop/lima/0/ha.sock: connect: connection refused]
Anything in 
ha.stderr.log
?
a
Nothing sticks out to me from today. Couple lines like this:
Copy code
{"level":"info","msg":"reloading dns nameservers to [192.168.1.1:53]","time":"2025-03-17T07:09:42-04:00"}
{"level":"info","msg":"reloading dns nameservers to []","time":"2025-03-17T08:10:47-04:00"}
p
That… doesn't sound like it should cause it to stop responding?
a
I wasn’t thinking that would be my problem. Just info messages.
lima.log has more stuff.
DM’d you that log file.
p
Yeah, nothing we don't already know about in there (the host agent isn't responding).
a
I’m gonna have to step away for a bit. I have a OS patch queued up. Maybe I’ll just let it install, get that full reboot, and see if things clear up on their own. Thanks for looking at this. I’ll let you know how things go.
p
Sure thing
a
I was on Rancher Desktop 1.17.1. The OS patch and system restart didn’t change anything. Tonight the update checker worked and told me to install 1.18.2, which I did. Everything started up fine after updating. 🤷
p
… Magic! (And yeah, the update server got fixed, yay)
11 Views
Open in Slack
PreviousNext
Powered by