Linux Agent discovery is getting stuck in pending state for a long time

Ravi Bhushan 41 Reputation points
2023-06-06T19:24:27.64+00:00

We are working on the migration of linux servers to another MG. Everything is in place like Port, Certificate, RDP, Unix/Linux Account and other checks as well, but when we are running the discovery through wizard or through the script it is getting stuck in pending state for a longer time and then getting failed. Can you please help me with this. Below is the screenshot:-

User's image

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,511 questions
Microsoft System Center
Microsoft System Center
A suite of Microsoft systems management products that offer solutions for managing datacenter resources, private clouds, and client devices.
1,033 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. XinGuo-MSFT 19,771 Reputation points
    2023-06-07T06:55:15.4633333+00:00

    Hi,

    Based on the context provided, it seems that the Linux Agent discovery is failing and getting stuck in the pending state for a long time. This may happen due to various reasons such as configuration issues, credential or privilege problems, or network and name resolution problems.

    To troubleshoot this issue, you can refer to the following article: "Troubleshoot UNIX/Linux agent discovery in Operations Manager" [1]. This article provides a detailed troubleshooting guide for common errors encountered during the discovery process of UNIX or Linux computers.

    References:

    1. Troubleshoot UNIX/Linux agent discovery in Operations Manager - https://learn.microsoft.com/en-us/troubleshoot/system-center/scom/troubleshoot-unix-linux-agent-discovery
    0 comments No comments

  2. SChalakov 10,396 Reputation points MVP
    2023-06-07T08:32:07.11+00:00

    Hi Ravi,

    let's start with some simple troubleshooting steps:

    • Is your SCOM MG up to date?
    • Very important: Are your Linux MPs also in their newest versions?
    • Did you try flushing the cache on your SCOM management servers, which are part of the Linux monitoring resource pool?
    • Are there any related events in the OpsMgr event log on those management servers?

    Regards,

    Stoyan

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.