Request: Incorrect core config doesn't max out CPU
Posted: Tue Feb 07, 2023 5:58 pm
Hi,
We've found that if the remote agent has an incorrect unimus.access.key, or the Unimus Core service cannot connect to the Unimus server on TCP port 5509, it seems to go into a tight loop using maximum CPU and makes the whole server unresponsive so we cannot logon and the server cannot respond to its normal functions.
This is a two-core VMware machine running Windows and Unimus Core version 2.2.4, and needed rebooting from the VMware console side, we think we have seen this behaviour on more than one system.
The logfiles do help troubleshoot it, but feature suggestion - detection failed connection to the main server and go into a sleep state with occasional retries or clean service shutdown instead.
We've found that if the remote agent has an incorrect unimus.access.key, or the Unimus Core service cannot connect to the Unimus server on TCP port 5509, it seems to go into a tight loop using maximum CPU and makes the whole server unresponsive so we cannot logon and the server cannot respond to its normal functions.
This is a two-core VMware machine running Windows and Unimus Core version 2.2.4, and needed rebooting from the VMware console side, we think we have seen this behaviour on more than one system.
The logfiles do help troubleshoot it, but feature suggestion - detection failed connection to the main server and go into a sleep state with occasional retries or clean service shutdown instead.