SCOM Linux parameter for Expression/Alert Description
Hi, I would like to know if there is a way to get more information from //*[local-name()="StdOut"] parameter. I know that it can be used in this way in Expression and $Data/Context///*[local-name()="StdOut"]$ in Alert. But I would like to forward little bit more info into Alert and Expression itself. For example got script which returns two values Uptime and LastBoot. And I would like to build the Expression based on Uptime and provide LastBoot into Alert description. I wonder if this is even possible in SCOM. Script itself : #!/bin/bash # Get uptime in seconds uptime_seconds=$(cat /proc/uptime | cut -d'.' -f1) # Get last boot time last_boot=$(who -b | awk '{print $3, $4}') # Output in the required format echo "Uptime : $uptime_seconds" echo "LastBoot : $last_boot" So I tried with //*[local-name()="StdOut"][contains(., "last_boot")]/text() $Data/Context///*[local-name()="StdOut"][contains(., "last_boot")]/text()$ But it doesn't work.SCOM Linux Parameter for Expression/Alert Description
Hi, I would like to know if there is a way to get more information from //*[local-name()="StdOut"] parameter. I know that it can be used in this way in Expression and $Data/Context///*[local-name()="StdOut"]$ in Alert. But I would like to forward little bit more info into Alert and Expression itself. For example got script which returns two values Uptime and LastBoot. And I would like to build the Expression based on Uptime and provide LastBoot into Alert description. I wonder if this is even possible in SCOM. Script itself : #!/bin/bash # Get uptime in seconds uptime_seconds=$(cat /proc/uptime | cut -d'.' -f1) # Get last boot time last_boot=$(who -b | awk '{print $3, $4}') # Output in the required format echo "Uptime : $uptime_seconds" echo "LastBoot : $last_boot" So I tried with //*[local-name()="StdOut"][contains(., "last_boot")]/text() $Data/Context///*[local-name()="StdOut"][contains(., "last_boot")]/text()$ But it doesn't work. Please support.
Linux Agent Install Failure - Certificate Issue
I'm attempting to install the Linux agent on a new AlmaLinux 9.5 server. The server replaced a previously monitored RHEL 8.10 server, and the new server has the same IP but a different hostname. The install fails with "Signed certificate verification operation was not successful - Object reference not set to an instance of an object." SCOM 2019 UR6 Hotfix - single management server Linux agent version 1.9.1-0 Telnet successful from SCOM management server to new host via TCP/22 and TCP/1270 Single forward DNS entry refers to new host FQDN Single reverse DNS entry for IP refers to new host - no other reverse entries for same IP Monitoring and action account credentials verified Sudoers taken from successful AlmaLinux 9.5 agent install omiengine, omiserver, and omiagent are running after the failed install /var/log/messages only SCOM-related error is "omid.service: Can't open PID file /var/opt/omi/run/omiserver.pid (yet?) after start: Operation not permitted", which I see on other systems with a successful agent installation /opt/microsoft/scx/bin/tools/scxadmin -status omiserver: is running omiagent: 1 instance running omiserver.log: 2025/03/09 19:45:03 [9217,9217] WARNING: null(0): EventId=30118 Priority=WARNING ssl-read error: 167772454 [error:0A000126:SSL routines::unexpected eof while reading] omiagent.root.root.log: 2025/03/09 19:45:06 [9389,9389] WARNING: null(0): EventId=30042 Priority=WARNING cannot open shared library: {/opt/omi/lib/libSCXCoreProviderModule.so}: libcrypt.so.1: cannot open shared object file: No such file or directory 2025/03/09 19:45:06 [9389,9389] WARNING: null(0): EventId=30041 Priority=WARNING cannot open shared library: {SCXCoreProviderModule}: SCXCoreProviderModule: cannot open shared object file: No such file or directory 2025/03/09 19:45:06 [9389,9389] WARNING: null(0): EventId=30065 Priority=WARNING failed to open provider library: SCXCoreProviderModule 2025/03/09 19:45:06 [9389,9389] ERROR: null(0): EventId=20001 Priority=ERROR Agent _RequestCallback: ProvMgr_NewRequest failed with result 1 !
create a SCOM monitor by referring a Rule
Hi, Is there any step by step guidance to create a SCOM Monitor by referring the existing performance collection rule. We have a Performance Collection rule which is collecting the metrics as expected and its used for creating dashboards. But now we have a requirement to create an alerting monitor based on that collected counter metric values from that Rule. I tried everywhere by no tutorials and use full links to refer. Please someone help.SSRS Reporting Services HTTP Error 503
In an attempt to repair a broken SSRS installation for Operations Manager, I have attempted a fresh install using SQL Reporting Services 2017 (14.0.600.1669). When running OM 2019 RTM Report Server (Setup version 10.19.10050.0) it changes the SRS extension in the rsreportserver.config, the ReportServer web service stops working with 503 error. Other discussions I have seen with similar issue suggested a newer version of SSRS (done) and others suggest turning off AV (done) and I am still seeing this issue. Does anyone else know how to troubleshoot why the OM Extension would be giving the ReportServer a 503 error? I am wondering if some other aspect of the server hardening could be impacting it? OPSMGRSETUPWIZARD.LOG [12:24:01]: Always: :Adding WebConfigAppSetting to WebConfigFile [12:24:02]: Debug: :Setting retry count to:5 [12:24:02]: Debug: :More: 5 rety to go.. [12:24:02]: Debug: :AddWebConfigAppSettingToWebConfigFile: Added AppSetting with a GroupId of 209e08e0-0bb9-516b-5c3c-256e32c99e8f in the C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\web.config config file. [12:24:02]: Always: :Adding WebConfigAppSetting to ReportingService config file [12:24:02]: Debug: :Setting retry count to:5 [12:24:02]: Debug: :More: 5 rety to go.. [12:24:02]: Debug: :AddWebConfigAppSettingToWebConfigFile: Added AppSetting with a GroupId of 209e08e0-0bb9-516b-5c3c-256e32c99e8f in the C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\bin\ReportingServicesService.exe.config config file. [12:24:02]: Always: :Replacing SRS extensions. [12:24:02]: Debug: :ReplaceSRSExtensionsWithOMExtensions: full SRS URL is : http://VSCOMSQL:80/ReportServer/ReportService2005.asmx [12:24:02]: Debug: :ReplaceSRSExtensionsWithOMExtensions: MOM Server is: vscom.greenfieldsavings.com [12:24:02]: Debug: :ReplaceSRSExtensionsWithOMExtensions: SRS Report Server Folder is: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\ [12:24:02]: Debug: :ReplaceSRSExtensionsWithOMExtensions: RSSrvPolicy.Config File: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\rsreportserver.config [12:24:02]: Debug: :Setting retry count to:5 [12:24:02]: Debug: :More: 5 rety to go.. [12:24:02]: Debug: :Setting retry count to:5 [12:24:02]: Debug: :More: 5 rety to go.. [12:24:03]: Debug: :ReplaceSRSExtensionsWithOMExtensions: Restarted the service: ReportServer [12:24:03]: Debug: :Setting retry count to:5 [12:24:03]: Debug: :More: 5 rety to go.. [12:24:04]: Warn: :Message:SRSPolicySetter WebException Exception: The request failed with HTTP status 503: Service Unavailable.. Will retry.. [12:24:04]: Debug: :Now Sleeping for : 60000 milliseconds [12:25:04]: Debug: :More: 4 rety to go.. [12:25:16]: Warn: :Message:SRSPolicySetter InvalidOperationException Exception: Client found response content type of '', but expected 'text/xml'. The request failed with an empty response.. Will retry..
Exclude Linux disk from monitoring
Hello, I get this message in SCOM and I want to exclude the disk from monitoring: The disk partitions breaching threshold are: Drive Name - Free space MB / - 7.94MB So, it's root and it is not neccessary to monitor / for a particular server. I have created an override for / but it doesn't work. The override value is only /. On other machines I have this override: /etc/resolv.conf|/boot/* this works. Could somone help to understand, why the override for / doesn't work? Thanks, Arne
MP issue - SQL management pack version 7.0.42.0
I have a problem with allway-on monitoring since I've installed the 7.0.42.0 version of the SQL MP. Since that time I got a lot of "MSSQL: Availability Group is not ready for automatic failover" alerts from the Availability Group Automatic Failover (rollup) monitor. When I open the health explorer of one of the alerts I see this (removed servernames): I discussed this with out database team, but they ensure there are no problems at all. Everything is working. Do more people issued this after applying this management pack? Kind regards, Mark
SCOM and SQL - Not able to disover
We built a SCOM 2022 environment with no issues in discovery all of our servers. I installed the SQL agnostic Managment Pack, latest version. I decided to leverage Kevin Holman's method of discovery SQL Server, avoiding the run as account. The SQL Seed Class is all Healthy. I checked the Registry to confirm, and all looks good. Next step is for the SQL team to create an account to create a HealthService Login. They did that and when I ran the task Create HealthService Login as Low Priv Task, it was successful. Ran the run-as Demand Database Discovery. Get no error message and but all the servers are showing Not Monitored. I ran it via manual SQL script and looks good, no error, but still I am getting "not monitored". Is there a log file that I can review or a method of seeing what is happening in the environment. I thought it might be network, but not sure. My second guess might be a group policy is preventing maybe a log on as a service, but that isn't the case and I set it up manually to log in as a service. It would be great if there was an error, so hoping that this process is captured in some log. I checked Agent Management logs, and it has no information at all regarding SQL discovery.SCOM - Enable "Database Backup Status" monitor for select databases
Hey there, I've got 8 SQL servers discovered in my environment and I'd like to enable the "Database Backup Status" monitor for all of the databases on 4 of those servers. I want to do this using a dynamic group so that I don't have to constantly manage the list of databases. I've tried several approaches but each of them has fallen short. Any thoughts on how I can approach this? TIA ~dgm~
MP Microsoft.Windows.Library version mismatch [7.5.8501.0]:[7.5.8501.1]
Subject is the message in events from the OperationsManager eventlog as Service Manager is trying to synchronise with SCOM. Normally not a biggie as you just import the same (or greater) version into SCSM and sync again, problem solved. I just cannot seem to be able to find version 7.5.8501.1 anywhere!? Spoke to the SCOM admins at this customer, and all they did was to upgrade to one of the Update Rollups, but this version is not available in the folder for updated management packs were we normally pick up these updates so we can make sure the sync will keep working. Where can I download this 7.5.8501.1 version of the Microsoft.Windows.Library version?
