"Failed to fetch system information message" error within the vRealize Lifecycle Manager (LCM) UI
search cancel

"Failed to fetch system information message" error within the vRealize Lifecycle Manager (LCM) UI

book

Article ID: 428284

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When attempting to view system details in the vRealize Lifecycle Manager (LCM) UI, the following error is displayed:

"Failed to fetch system information message"

This error prevents the loading of critical system metrics, such as disk usage and CPU statistics.

In the /var/log/vrlcm/vmware_vrlcm.log file, you see an exception similar to the following:

ERROR [exec-id] c.v.v.l.l.s.ProductPolicyServiceImpl -  -- Exception occurred when acquiring the SDDC Manager token. java.net.SocketTimeoutException: Read timed out

 

Environment

VMware Aria Suite Lifecycle 8.x

Cause

This issue occurs due to incorrect DNS configuration on the vRealize Lifecycle Manager appliance. Specifically, if the DNS infrastructure has been updated but the appliance's /etc/resolv.conf (or related systemd-resolved configuration) still points to invalid or unreachable nameservers, the appliance cannot resolve the necessary hostnames to fetch system information.

Resolution

To resolve this issue, verify the network connectivity and update the DNS settings on the appliance.

Step 1: Verify Network Connectivity

You can confirm the connectivity issue by attempting to connect to the remote system from the LCM appliance using nc (netcat).

  1. SSH into the vRealize Lifecycle Manager appliance.

  2. Run the following command:

    nc -vz <HOST> <PORT>
    

    Replace <HOST> and <PORT> with the target system's details.

If the command does not return a response (hanging until Ctrl-C is pressed), it indicates a network or DNS resolution failure.

Step 2: Verify DNS Configuration

Check the current DNS configuration to see if the nameservers are correct for your environment.

  1. Inspect the resolution configuration file:

    cat /etc/resolv.conf
    
  2. Verify if the nameserver entries match your current infrastructure requirements.

Step 3: Reconfigure DNS

If the DNS settings are incorrect, you must reconfigure them using the supported method for the appliance. Do not manually edit /etc/resolv.conf as changes may not persist or work correctly with systemd-resolved.

Follow the instructions in the official Broadcom documentation: Reconfigure DNS and Domain Search on the vRealize Lifecycle Manager Appliance

After updating the DNS settings, reload the LCM UI. The system information should now populate correctly.

Additional Information

This article is a fork from https://knowledge.broadcom.com/external/article/387688/failed-to-fetch-system-information-messa.html. If you are experiencing this issue, you might also check this KB.