Skip to main content
NetApp Knowledge Base

Manually deployed connector unstable after CVO discovery

  1. Last updated
  2. Save as PDF
Views:
72
Visibility:
Public
Votes:
0
Category:
netapp_console
Specialty:
ds_cvo
Last Updated:

Applies to

NetApp Console (Formerly BlueXP) 3.9.43 and later
Manual Console Agent (Formerly Connector) Installation
RedHat Enterprise Linux (RHEL)
Azure

Issue

Manual deployment of an Azure console agent fails in random steps after a CVO has been discovered.

Cause

The Console Agent was deployed using the NetApp documentation.   
 
  • Site requirements dictated that SELinux and a firewall needed to be implemented for any deployed appliance VM.
  • A firewall was in place that was blocking access to the 
  • Additionally, the deployed RHEL VM had implemented Podman  Container Networking Interface (CNI).
  • OCCM logs from the Agent (connector) ASUP shows a memory exhaustion event:
        
        2025-09-22T08:02:18.105378304+00:00 stdout F [ERROR] [SECURITY][09/22/2025 08:02:18.055] [oncloud-akka.actor.default-dispatcher-2526] [akka.actor.ActorSystemImpl(oncloud)] Uncaught error from thread [oncloud-akka.actor.default-dispatcher-2526]: unable to create new native thread, shutting down ActorSystem[oncloud]
    2025-09-22T08:02:18.105378304+00:00 stdout F java.lang.OutOfMemoryError: unable to create new native thread
        
        which corresponds to observed times that the Console would lose functionality.

Solution

As directed by NetApp Cloud engineering, the following steps were performed to resolve the issue:
 
  • SELinux was disabled for the deployed VM
  • The site firewall was modified to allow all of the required elements for the Console Agent.
  • The Podman network backend was switched to NetAvark and Aardvark DNS.
  • The number of allowed concurrent threads for the Agent was increased from the default of 2048 to 10000.  Comntact Technical Supporrt for instructions on this step.

Partner Notes

None.
 

Additional Information

None.

Internal Notes

Engineering provided these steps via CPE-9618 to modify the default number (usually 2048) of threads configured in the Podman connector.
  1. Backup and then edit the /usr/share/containers/containers.conf file.
  2. Within that file locate and add the following lines above the  [engine] section:

[containers]
pids_limit = 10000    (This can be set to a value of -1, which will provide for unlimited threads)

  1.  Restart the subsystem with:  sudo systemctl restart podman
  2. Navigate to /opt/application/netapp/service-manager-2 where the docker-compose.yml file is present and run:

sudo podman-compose down
sudo podman-compose up -d

 

Additionally, feature request UMF-7007 has been opened to provide for a publication of the need for additional resources going forward for newer versions of the Console Agent as new features and function are implemented.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.