Skip to main content

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

Resolving vCenter Network Enumeration Stack Overflow Error in Aria Automation


Issue/Introduction

This article addresses a stack overflow error encountered in Aria Automation when enumerating a large number of NSX networks (over 1000) from vCenter. This error can prevent Aria Automation from collecting network information and lead to incomplete provisioning or configuration issues.

The error from the provisioning logs:

####-##-##T##:##:##Z ERROR provisioning [host='provisioning-service-app-123456-1234' thread='vsphere-enum-205' user='' org='' trace='' parent='' span=''] c.v.p.c.m.a.v.e.DatacenterEnumerationService.lambda$processNetworks$23:752 - [FQDN]:[/resources/endpoints/123456-1234-1234-1234-123456]: Failed collecting networks: java.util.concurrent.CompletionException: java.lang.StackOverflowError
 at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
 at java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:687)
 at java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:662)
 at java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2168)
 at com.vmware.photon.controller.model.adapters.vsphere.remotecallmanager.vc.PcDomain.handleRetrieveResults(PcDomain.java:426)
 at com.vmware.photon.controller.model.adapters.vsphere.remotecallmanager.vc.PcDomain.lambda$handleRetrieveResults$13(PcDomain.java:441)
 at java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)

Environment

Aria Automation 8.16.x

Cause

Aria automation handles the recursive retrieval of network properties from vCenter using the "retrievePropertiesEx" method. This recursive approach can cause a stack overflow error when dealing with extensive network inventories.

Resolution

The recommended solution is to upgrade Aria automation to version 8.16.1 or later. This version includes a fix that addresses the stack overflow issue:

1. The network enumeration implementation is changed from a recursive approach to an iterative one, eliminating the risk of stack overflow.
2. The page size for retrieving results from vCenter is increased from 25 to 100, reducing the number of API calls required.

Additional Information

Upgrading to Aria Automation 8.16.1 offers additional benefits beyond resolving the stack overflow error. It's recommended to review the Aria Automation 8.16.1 release notes for details on other improvements and bug fixes.

Comments

Post a Comment

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...
Post a Comment
Read more

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...
Post a Comment
Read more
  vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...
Post a Comment
Read more