https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
You may want to try 
rdctl shutdown
to see if that still allows you to stop the app "normally" before killing processes selected via 
grep
...
✅ 1
The relevant logs would be in 
~/Library/Logs/rancher-desktop
. If you collect them in a zip file/tarball, make sure the symlinks are stored as files and not symlinks...
✅ 1
c
Putting this here for my reference when the time comes... 
tar -hcf rancher-desktop-logs.tar ~/Library/Logs/rancher-desktop
f
Just out of curiosity: Does your Mac go to sleep before Rancher Desktop becomes unresponsive? Or does this happen during regular usage?
c
Typically normal usage. It just happened when I disconnected from my Docking station...
Current state is: 
❯ docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
rdctl shutdown
worked instead of killing the processes
rancher-desktop-logs.tar
Copy code
❯ rdctl shutdown
INFO[0000] Sending SIGINT to hostagent process 96029
INFO[0000] Waiting for the host agent and the driver processes to shut down
INFO[0000] [hostagent] 2023/12/14 14:47:36 tcpproxy: for incoming conn 127.0.0.1:51387, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: connection was refused
INFO[0000] [hostagent] 2023/12/14 14:47:46 tcpproxy: for incoming conn 127.0.0.1:51394, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: connection was refused
INFO[0000] [hostagent] Received SIGINT, shutting down the host agent
INFO[0000] [hostagent] Shutting down the host agent
INFO[0000] [hostagent] Stopping forwarding "/var/run/docker.sock" (guest) to "/Users/david.hoffman/.rd/docker.sock" (host)
INFO[0000] [hostagent] Stopping forwarding "/run/lima-guestagent.sock" (guest) to "/Users/david.hoffman/Library/Application Support/rancher-desktop/lima/0/ga.sock" (host)
INFO[0000] [hostagent] Shutting down VZ
ERRO[0001] [hostagent] dhcp: unhandled message type: RELEASE
INFO[0003] [hostagent] [VZ] - vm state change: stopped
ERRO[0003] [hostagent] accept tcp 127.0.0.1:51377: use of closed network connection
INFO[0004] Stopping socket_vmnet daemon for "rancher-desktop-shared" network
INFO[0004] Stopping socket_vmnet daemon for "rancher-desktop-bridged_en8" network
It has happened again. I made sure this time that my network was stable connected only to wire networking and it worked fine for several hours but has failed again. Current state:
Copy code
❯ docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
rdctl shutdown
did not work this time
Copy code
❯ ps -ef | grep rancher
    0 46732     1   0  9:15AM ??         0:00.01 sudo --user root --group wheel --non-interactive /opt/rancher-desktop/bin/socket_vmnet --pidfile=/private/var/run/rancher-desktop-bridged_en8_socket_vmnet.pid --socket-group=everyone --vmnet-mode=bridged --vmnet-interface=en8 /private/var/run/socket_vmnet.rancher-desktop-bridged_en8
    0 46736 46732   0  9:15AM ??         1:07.11 /opt/rancher-desktop/bin/socket_vmnet --pidfile=/private/var/run/rancher-desktop-bridged_en8_socket_vmnet.pid --socket-group=everyone --vmnet-mode=bridged --vmnet-interface=en8 /private/var/run/socket_vmnet.rancher-desktop-bridged_en8
Unfortunately my script to gather info was too agressive and resulted in an empty set of logs, I will have to wait for next event.
Continuing this thread, I am continuing to have a problem that presents itself with a random loss of the docker.sock. I am running v1.11.1 on a Mac M2 (currently Sonoma 14.2.1) with 32 GB RAM. I originally thought it might be connected to docking/undocking, but it is happening when I am just sitting here not doing anything. (I should note that way I KNOW it has failed is that my VSCODE DevContainers environment fails, so I guess it is not doing anything, as there is a container running in it for the DevContainer) There is no rhyme or reason to it happening. I have seen other reports that this happens when the mac goes to sleep, but I have configured my machine to prevent that to rule that out and the issue is still occurring. I have captured the logs from the latest event and attached them to this message.
rancher-desktop-logs.tar
Continuing this thread, I am continuing to have a problem that presents itself with a random loss of the docker.sock. I am running v1.11.1 on a Mac M2 (currently Sonoma 14.2.1) with 32 GB RAM. Volumes - virtiofs Emulation - VZ Container Engine - dockerd Kubernetes - Enabled v1.27.5 I originally thought it might be connected to docking/undocking, but it is happening when I am just sitting here not doing anything. (I should note that way I KNOW it has failed is that my VSCODE DevContainers environment fails, so I guess it is not doing anything, as there is a container running in it for the DevContainer) There is no rhyme or reason to it happening. I have seen other reports that this happens when the mac goes to sleep, but I have configured my machine to prevent that to rule that out and the issue is still occurring. I have captured the logs from the latest event and can provide privately if needed. Any assistance that can be offered would be greatly appreciated
7 Views
Open in Slack
PreviousNext
Powered by