In certain environments, vxconfigd memory utilization may gradually increase over time, particularly when VxVM commands are executed frequently through monitoring tools, health checks, or automation scripts
The rate of memory increase can vary depending on the frequency of these command executions. In environments with frequent VxVM command activity, the memory footprint of vxconfigd may become noticeable over several days or months.
The issue occurs due to memory leak in the licensing library (liblicmgr72.so) and liblicmgr72.dll (Windows Platform) - each client connection triggers multiple license checks that allocate memory but never releases it.
This leak accumulates with every vx* command execution.
Affected version
Linux
7.4.2.5900
8.0.0.4100
8.0.2.3500
8.0.2.3600
9.0.7
9.2
9.2.1
Unix
9.0.7
8.0.2.3500
8.0.0.4100
7.4.2.5900
Windows
9.2.0
9.0.7
8.0.20100
8.0.00100
7.4.20100
The Product Engineering team currently plans to address this issue through a patch or hotfix in the current software versions. However, for the latest version, it is scheduled to be resolved in the 9.2.2 release.
Please note that the Product Engineering team reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Our plans are subject to change, and any actions you take based on this information, or your reliance on it, are at your own risk.
As a workaround , ensure controlled restart of vxconfigd when memory exceeds a safe threshold, ensuring no configuration changes are in progress.
Memory leak observed for vxconfigd post upgrade to Infoscale License Enforcement patches
Feedback submitted!