We have server in PIN secured network and we're monitoring that through the SCOM Gate server, Suddenly the monitored server thrown the alert for High CPU Utilization and it cause of SCOM's Monitoringhost.exe
Help here please....
We have server in PIN secured network and we're monitoring that through the SCOM Gate server, Suddenly the monitored server thrown the alert for High CPU Utilization and it cause of SCOM's Monitoringhost.exe
Help here please....
@ShivaRavichandran-6199, From your description, I know the MonitoringHost.exe consumes high CPU on SCOM Gateway server with Windows Server 2008 R2 Version. If there's any misunderstanding, please let us know.
For windows server 2008 R2, there's some known issue with CPU. we can see if it met our situation:
https://support.microsoft.com/en-us/topic/operations-manager-agents-consume-100-percent-of-cpu-resources-for-the-monitoringhost-exe-process-a0523d63-aead-a4cf-0a29-387b7147ed49
https://support.microsoft.com/en-us/topic/the-monitoringhost-exe-process-may-consume-all-the-cpu-resources-when-a-large-amount-of-performance-data-is-created-by-using-a-managed-data-source-module-in-system-center-operations-manager-2007-02b514c3-9c69-a2ab-d03c-63f4d177c4a3
However, if it is not, could you collect the following information to clarify?
1. Could you let us know the SCOM version?
2. When did this issue happen? Have we changed anything before the issue occurring? Have we imported any new MPs?
3. Check the Operations Manager event log during the high CPU time to see if there's any finding.
Meanwhile, we suggest to install all the latest hotfixes for the Windows 2008 R2 server and clear cache to see if it can help.
https://docs.microsoft.com/en-us/system-center/scom/manage-clear-healthservice-cache?view=sc-om-2019
If there's any update, feel free to let us know.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Crystal,
As it is a client monitored server under SCOM monitoring and not a SCOM gateway server, the server runs on the Windows 2008 R2...
Thanks for the suggestions please....
Could you let us know the SCOM version? SCOM 2016 UR10
When did this issue happen? Started this Week
Have we changed anything before the issue occurring? No, Nothing
Have we imported any new MPs? We haven't imported any MP's recently
Check the Operations Manager event log during the high CPU time to see if there's any finding.,
@ShivaRavichandran-6199, Thanks for the correction. From your description, I know the issue started this week without any change. Here, we suggest to schedule a non-business time to restart the server to see if the issue will disappear.
However, if the issue still persists, we suggest to install the latest update for windows server 2008 R2 to see if this can help.
If there's any update, feel free to let us know.
@ShivaRavichandran-6199, Hope things are going well. I am writing to see if we have the opportunity to restart the server and how's the result. If there's any update, feel free to let us know.
As pre Crystal mention, there is a known issue in early version of SCOM. As a result, please update the latest CU for your SCOM environment and also apply latest update on windows environment. Moreover, i want to know more detail information for this
1. what is the version of SCOM
2. any error log in event log
3. on agent machine
Stop Microsoft monitoring agent service
Remove the folder %systemdrive\Program Files\Microsoft Monitoring Agent\Agent\Health Service State
Restart Microsoft Monitoring agent service
Roger
Hi Roger,
We are from the same team. We tried the steps suggested by you but unfortunately this does not bring down the CPU.
We use SCOM 2016 with UR10.
No error as such, CPU utilization is high and it is consumed by MonitoringHosts.exe. Please let me know if you have any other solution.
6 people are following this question.