Linux Server Monitoring in SCOM 2019 with OMSAgent Version 1.12.15-0

Question

Upon successful discovery of Linux servers in SCOM 2019 running on Red Hat Enterprise Linux 7 with OMSAgent version 1.12.15-0, the servers do not transition to a healthy state as expected. Instead, they remain in a greyed-out state or show as not monitored within the SCOM console.

Attempts to restart the agent using the 'scxadmin' command do not resolve the issue, as the agent remains in a stopped state indefinitely.

Answer 1

Hi,

It sounds frustrating to have your Linux servers not transitioning to a healthy state in SCOM 2019. Here are some steps and considerations that might help resolve the issue:

• Ensure that the SCOM management server can communicate with the Linux servers. Verify network connectivity and firewall settings.
• Use the scxadmin command to check the status of the agent. If the agent is stopped, try starting it manually and check for any error messages:

 sudo /opt/microsoft/scx/bin/tools/scxadmin -status
 sudo /opt/microsoft/scx/bin/tools/scxadmin -start

• Check the OMSAgent logs for any errors or warnings that might indicate why the agent is not starting. Logs are typically located in /var/opt/microsoft/scx/log.
• Verify that the appropriate management packs for monitoring Linux servers are imported and configured correctly in SCOM.
• Clearing the agent cache can sometimes resolve issues with agents not reporting correctly:

sudo rm -rf /var/opt/microsoft/scx/cache/* 
sudo /opt/microsoft/scx/bin/tools/scxadmin -restart

Feel free to ask if you need further assistance or have any other questions!