So one of the issues is that the system seems to get slower over time. I notice it mainly though response time when I use DomoPad and turn on or off devices, or responsiveness of DomoPad control pages on my tablets. Also my DSC plugin fails to connect to my Envisalink EVL-4 very often, and the DSC plugin stops and then restarts, and this goes on. There can be periods when all works fine for a while, then it starts to happen again. I have tried to reboot the EVL-4 (many times) since I know that it can only have one connection and to avoid that a hanged session/connection causes the issue. All this worked very well before upgrading to 2022.2, but it could be a coincidence.
Searching for clues, I looked at the Activity Monitor and noticed that plugin CPU consumption rises quite much over time for one of the IndigoPluginHost3 processes (that's why I post in this forum and not the DSC (this time) or DomoPad forum). After a restart of the Indigo server, the highest CPU for one of the IndigoPluginHost3 processes is around 20-30%, but after a few days it is up to 80-90%. Is this normal?
See attached screenshots, the lower CPU consumption is directly after a Indigo server start, and the other with higher CPU consumption is after some days.
The error message from DSC plugin is:
- Code: Select all
DSC Alarm Initializing communication at address: 192.168.xxx.xxx:4025
DSC Alarm Communication established
DSC Alarm Error Connection RX Error: read failed: [Errno 54] Connection reset by peer
DSC Alarm Error Connection TX Error: write failed: [Errno 32] Broken pipe
Error plugin "DSC Alarm 2022.0.6" (pid 69047) unexpectedly stopped -- restarting in 5 seconds
DSC Alarm Initializing communication at address: 192.168.xxx.xxx:4025
DSC Alarm Communication established
DSC Alarm Error Connection RX Error: read failed: [Errno 54] Connection reset by peer
DSC Alarm Error Connection TX Error: write failed: [Errno 32] Broken pipe
Error plugin "DSC Alarm 2022.0.6" (pid 69158) unexpectedly stopped -- restarting in 20 seconds
Reloading plugin "DSC Alarm 2022.0.6" using API v3.0
Starting plugin "DSC Alarm 2022.0.6" (pid 69164)
Started plugin "DSC Alarm 2022.0.6"
DSC Alarm
==================== Initializing New Plugin Session ======================================================
Plugin name: DSC Alarm
Plugin version: 2022.0.6
Plugin ID: com.frightideas.indigoplugin.dscAlarm
Plugin Log Level: Info
Indigo version: 2022.2.2
Python version: 3.10.2 (v3.10.2:a58ebcc701, Jan 13 2022, 14:50:16) [Clang 13.0.0 (clang-1300.0.29.30)]
Mac OS Version: 12.6.8
Process ID: 69164
===========================================================================================================
DSC Alarm Initializing communication at address: 192.168.xxx.xxx:4025
DSC Alarm Error Error opening socket: Could not open port socket://192.168.xxx.xxx:4025: timed out
DSC Alarm Warning Plugin will attempt to re-initialize again in 3 minutes.
The pid is not the one consuming much CPU and is only active for a short time.
When I reboot the Mac AND the EVL4 at the same time it usually works for a while...
I don't know if these thing are in any way related, but there is something strange going on. Could it be that something happened with the 2022.2 upgrade, some process still running from the previous version (even though I reinstalled MacOS)?
How would I go forward finding the issue?
If this is posted in the wrong forum, go ahead and move it please.
