MiniUnifi intermittently failing on new (to me) iMac

I have no idea why this is happening. I've tweaked the code a bit to try to keep the plugin from crashing when it happens:

https://github.com/FlyingDiver/Indigo-m ... /tag/0.1.4

I appreciate you trying. Installed. I'll let you know how it goes.

Didn't take long this time. Interesting that the first failure seemed to resolve (I'm assuming) with the retry in 10 seconds, and no other plugins were affected. But then two minutes later the whole usual string of plugins all experienced failures in the usual order.

Also it's interesting that my remote Indigo console disconnected when this happened. I've seen that fairly often when this happens.

I think, despite the fact that it's always the miniUnifi plugin that's affected first, there may be something wrong with the OS and/or networking setup on this iMac. Everything was 100% fine on my old iMac. I'm not sure what to look for though. I think I'll start with disconnecting ethernet and turning on WiFi. That could rule out a couple of things on the network side.

Any other ideas?

Feb 7, 2022 at 11:46:01 AM
miniUniFi Error Error in plugin execution runConcurrentThread:

Traceback (most recent call last):
File "plugin.py", line 126, in runConcurrentThread
File "plugin.py", line 438, in updateUniFiDevice
StandardError: ServerCommunicationError -- timeout waiting for response

miniUniFi Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
Trigger Washing Machine Active

Feb 7, 2022 at 11:47:55 AM
miniUniFi Error Error in plugin execution runConcurrentThread:

Traceback (most recent call last):
File "plugin.py", line 126, in runConcurrentThread
File "plugin.py", line 438, in updateUniFiDevice
StandardError: ServerCommunicationError -- timeout waiting for response

miniUniFi Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
Sonos Error Error in plugin execution runConcurrentThread:

Traceback (most recent call last):
File "plugin.py", line 47, in runConcurrentThread
File "/Library/Application Support/Perceptive Automation/Indigo 2021.2/Plugins/Sonos.indigoPlugin/Contents/Server Plugin/Sonos.py", line 384, in runConcurrentThread
File "/Library/Application Support/Perceptive Automation/Indigo 2021.2/Plugins/Sonos.indigoPlugin/Contents/Server Plugin/Sonos.py", line 634, in updateRelTime
StandardError: ServerCommunicationError -- timeout waiting for response

Sonos Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
AD2USB Alarm Interface Error Error on line 749
AD2USB Alarm Interface Error panelMsgRead: Error: ServerCommunicationError -- timeout waiting for response
AD2USB Alarm Interface Error Error on line 749
AD2USB Alarm Interface Error panelMsgRead: Error: ServerCommunicationError -- timeout waiting for response
AD2USB Alarm Interface Error Error on line 749
AD2USB Alarm Interface Error panelMsgRead: Error: ServerCommunicationError -- timeout waiting for response
Sonos SoCo Reactor Ignition...
Indigo Cocoa client disconnected (192.168.0.13)

Feb 7, 2022 at 11:48:41 AM
Z-Wave received "Garage Temp" sensor update to 50.5 °F

The error was in a different part of the code this time, but it's still at a point where the plugin has to communicate wit the main server process, and it's failing. It's inter-process communication, so unlikely to be networking, unless there's something really weird going on. Which there might be.

Do you have both ethernet and Wifi enabled on this machine at the same time? That's usually not a good idea. If only one, then switching to the other might provide useful info.

Also, check Console.app to see if there's any significant errors being reported. There might be something at the OS level at the time this is happening.

Do you have both ethernet and Wifi enabled on this machine at the same time? That's usually not a good idea. If only one, then switching to the other might provide useful info.

No, I'm careful to only use one or the other at a time for that very reason.

Also, check Console.app to see if there's any significant errors being reported. There might be something at the OS level at the time this is happening.

At first glance, the only suspicious thing I see in the Console app is a constant and unending stream of these messages in launchd.log:

Code: Select all

2022-02-07 11:45:37.484513 (user/501/com.apple.TrustEvaluationAgent [32236]) <Notice>: service exited: dirty = 0, supported pressured-exit = 0
2022-02-07 11:45:37.484523 (user/501/com.apple.TrustEvaluationAgent [32236]) <Notice>: exited due to exit(0)
2022-02-07 11:45:37.484525 (user/501/com.apple.TrustEvaluationAgent [32236]) <Notice>: service state: exited
2022-02-07 11:45:37.484528 (user/501/com.apple.TrustEvaluationAgent [32236]) <Notice>: internal event: EXITED, code = 0
2022-02-07 11:45:37.484530 (user/501) <Notice>: service inactive: com.apple.TrustEvaluationAgent
2022-02-07 11:45:37.484539 (user/501/com.apple.TrustEvaluationAgent [32236]) <Notice>: service state: not running
2022-02-07 11:45:47.106773 (user/501) <Warning>: failed lookup: name = com.apple.TrustEvaluationAgent, flags = 0x9, requestor = IndigoPluginHos[31116], error = 1: Operation not permitted
2022-02-07 11:45:47.106802 (gui/501 [100006]) <Warning>: failed lookup: name = com.apple.TrustEvaluationAgent, flags = 0x9, requestor = IndigoPluginHos[31116], error = 1: Operation not permitted
2022-02-07 11:45:47.106970 (user/501/com.apple.TrustEvaluationAgent) <Notice>: internal event: WILL_SPAWN, code = 0
2022-02-07 11:45:47.106978 (user/501/com.apple.TrustEvaluationAgent) <Notice>: service state: spawn scheduled
2022-02-07 11:45:47.106980 (user/501/com.apple.TrustEvaluationAgent) <Notice>: service state: spawning
2022-02-07 11:45:47.106991 (user/501/com.apple.TrustEvaluationAgent) <Notice>: launching: ipc (mach)
2022-02-07 11:45:47.107866 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: xpcproxy spawned with pid 32241
2022-02-07 11:45:47.107879 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: internal event: SPAWNED, code = 0
2022-02-07 11:45:47.107882 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: service state: xpcproxy
2022-02-07 11:45:47.107907 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: internal event: SOURCE_ATTACH, code = 0
2022-02-07 11:45:47.113912 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: service state: running
2022-02-07 11:45:47.113923 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: internal event: INIT, code = 0
2022-02-07 11:45:47.113928 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: Successfully spawned trustevaluationagent[32241] because ipc (mach)
2022-02-07 11:45:47.165083 (user/501) <Warning>: failed lookup: name = com.apple.TrustEvaluationAgent, flags = 0x9, requestor = IndigoPluginHos[31116], error = 1: Operation not permitted
2022-02-07 11:45:47.165097 (gui/501 [100006]) <Warning>: failed lookup: name = com.apple.TrustEvaluationAgent, flags = 0x9, requestor = IndigoPluginHos[31116], error = 1: Operation not permitted
2022-02-07 11:46:07.171555 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: service exited: dirty = 0, supported pressured-exit = 0
2022-02-07 11:46:07.171566 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: exited due to exit(0)
2022-02-07 11:46:07.171569 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: service state: exited
2022-02-07 11:46:07.171571 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: internal event: EXITED, code = 0
2022-02-07 11:46:07.171573 (user/501) <Notice>: service inactive: com.apple.TrustEvaluationAgent
2022-02-07 11:46:07.171583 (user/501/com.apple.TrustEvaluationAgent [32241]) <Notice>: service state: not running

I've mentioned this before on another thread having to do with Indigo on Monterey, but never got any sort of diagnosis. Do you see these messages on your system?

No, nothing like that.

OK, I'll start a new thread on it and see if I can get any attention.

viewtopic.php?f=131&t=25865

This issue has me stumped. I've noticed that every time the string of failures occurs in Indigo, the remote Indigo console I have connected on another computer also disconnects. And if I'm using the other computer at the time, I also see Finder warnings about mounted iMac volumes becoming unavailable.

So this seems to obviously be a networking issue. It happens with both WiFi and Ethernet (one at a time), so it's not a bad switch or port or something. But strangely, if I leave a continuous ping running on the iMac, it doesn't show any interruption. So that points to a software thing on the iMac. And I've wiped and reloaded Mac OS, so it's not something corrupted there.

I'll keep looking at it.