jay (support) wrote:
So, the server wasn't responding/hung up. Again, diagnosing the actual problem is where I'd start. If it was the memory bug above, then until we find and fix the problem the solution is to just make sure the Mac client isn't running when you don't need it.
BTW, just to let everyone know, this bug doesn't appear to be super widespread, possibly because many of you don't leave the client running all the time. I leave mine on all the time on my production server and never see the issue.
It very well may have been from the Indigo Client app running on my mac server, though I have never encountered this until 2 or 3 times in the past several months. I have been using 7.2 during this time, but I have also been doing a LOT of new stuff on Indigo, so I do not want to point fingers at 7.2. I also started using Grafana in this time span, which could be using up some resources vis a vis the influxdb.
Just to be clear about the symptoms:
1. Unable to log on via my lan, or via wan
2. On one occasion (but not other), was able to VNC into machine and restart Indigo Server, fixing the problem. The other time I needed to fix it remotely, I could not VNC in OR ssh in to my mac server. That said, Indigo Server was still running, as evidenced by updating logs and my motion-activated lights working appropriately. Restarting Indigo Server again fixed it.
3. The server mac still showed as an active client on my Unifi Cloud Key.
I know, this could be a million things. Still wondering about the reboot practice in general.