macOS: 10.4, 10.3, 10.2
This started with just one Hamachi installation but is now happening with multiple Hamach installations. When I try to connect to a remote peer the network is good (green dot) but the peer is not available (clear dot). On the peer system one or more of the Hamachi processes (LogMein Hamachi, LogmeIn Hamachi Menubar, and/or hamachid) show a CPU % of 99% or higher. Using the Acivity Monitor to force quit these processes will fix the issue, or a system reboot.
This seems to happen eventually to any system running Hamachi longer than a few weeks, which is problematic.
I think we've tried everyting, reinstalling Hamachi, macOS, complete reformat and reinstall of OS and Hamachi, paid accounts, free accounts, etc.
I've tried to find a corrolation to the type of networking setup and/or intenet connection, but no luck, it rains on the just and unjust alike. It does seem less likely to affect new Mac hardware and new macOS', but that's imperical so far, most of our installs are pre-2018 Mac minis, many of which can't run Mojave.
@maxwellk2 Sorry about that. If those OS are accurate, and you didn't mean 10.12 & 10.13, then we may be far outside of supported territory from Apple. In your case, you might be able to run a modified Linux version of Hamachi, but I'm not exactly sure what the end result would be.
Ah great, but weird, we're regulalry checking for updates but Hamachi is saying "You are already running the latest version of Hamachi." We've downloaded the new version and will give it a try.
@maxwellk2 In that case, try the new version 827 and see if that helps. If not, we can open up a case in support when you have direct access to those Macs.
Is there something we can do to capture begugging info when Hamachi locks up like this? Usually we're in a hurry to restore Hamachi, and don't have remote access, so we can't do a lot of tinkering when it happens.
We often have the remote user in the Activity Monitor already, getting them to save a sample of the hamachid process wouldn't be that many more steps prior to force quitting it.
@maxwellk2 The general area for LMI Hamachi logs is found in C:\Windows\ServiceProfiles\LocalService\AppData\Local\LogMeIn Hamachi ...
You'll want to work with a support specialist though, in case they need additional data to troubleshoot your problem: https://help.logmein.com/pkb_Home?l=en_US&c=products%3Almihamachi2
@AshC LogMeIn Hamachi for Mac 220.127.116.117 doesn't seem to address the issue we're still seeing. Many of our Hamachi peers, within a couple weeks, show the hamachid process hit 99% CPU load and become unresponsive. The easy fix is to ask the peer to restart their computer, if the peer is savvy enough we have them kill the hamachid process via the Activity Monitor.
The challenge with debugging is that it's random, and when it happens we need to get the peer working again right away.
What do you recommend? Happy to open a case as we'd like to get a resolution. One of our techs is working on an AppleScript to streamline the reset, but we'd rarther not have to rely on that.