Skip to main content

 vCenter data collection fails with UNKNOWN_SYSTEM_ERROR while fetching the content library in Aria Suite LCM

https://knowledge.broadcom.com/external/article?articleNumber=389911

Issue/Introduction

  • vCenter data collection fails  UNKNOWN_SYSTEM_ERROR while fetching the content library.
  • Multiple attempts result in the same error.
  • Logs show below error: 

ERROR vrlcm[1270] [scheduling-1] [c.v.v.l.a.c.EventProcessor] – java.lang.NullPointerException
INFO vrlcm[1270] [scheduling-1] [c.v.v.l.p.a.s.Task] – Injecting task failure event. Error Code : 'UNKNOWN_SYSTEM_ERROR', Retry : 'false', Causing Properties : '

{ CAUSE :: }

'
java.lang.NullPointerException: null
at com.vmware.vrealize.lcm.automata.core.EventProcessor.invokeTask(EventProcessor.java:366) [vmlcm-engineservice-core-8.18.0-SNAPSHOT.jar!/:?]
at com.vmware.vrealize.lcm.automata.core.EventProcessor.processEvents(EventProcessor.java:173) [vmlcm-engineservice-core-8.18.0-SNAPSHOT.jar!/:?]
at jdk.internal.reflect.GeneratedMethodAccessor162.invoke(Unknown Source) ~[?:?]
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:?]
at java.base/java.lang.reflect.Method.invoke(Unknown Source) ~[?:?]
at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84) [spring-context-5.1.17.RELEASE.jar!/:5.1.17.RELEASE]
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-5.1.17.RELEASE.jar!/:5.1.17.RELEASE]
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:?]
at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source) [?:?]
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
at java.base/java.lang.Thread.run(Unknown Source) [?:?]

Environment

  • VMware Aria Suite LifeCycle 8.18.x

Cause

  • The issue occurs due to a known bug in the vmlcm-service-8.18.0-SNAPSHOT.jar file.
  • The existing JAR file cannot fetch the content library due to a defect property. 
  • Replacing the JAR file and restarting the service resolves the issue.

Resolution

  • Take a snapshot of Aria LCM. 
  • Download the updated vmlcm-service-8.18.0-SNAPSHOT.jar file (Open a SR with GSS to get the file) 
  • SSH into vRSLCM as root.
  • Backup the existing JAR file from /var/lib/vrlcm.
  • Replace it with the new downloaded JAR file.
  • Restart the vRSLCM service using:
    systemctl restart vrlcm-server
  • Verify the service status:
    systemctl status vrlcm-server
  • Once the UI is accessible, retry the vCenter data collection.

Comments

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...