Spooler is consuming high memory
search cancel

Spooler is consuming high memory

book

Article ID: 429093

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We have some file servers where the **Nimsoft spooler is consuming high memory**, which is causing frequent server hangs. Despite making the following changes, the issue is still persisting:

Increased the message bulk limit to 500
Restarted the Nimsoft services
However, we are still observing high memory usage on the spooler.

Environment

UIM 23.4.x

Robot :23.4.x

 

Resolution

Below errors seen in the robot spooler logs and also observed the plugin_metric.cfg is missing on the server

Feb 12 01:12:20:752 [6780] 0 spooler: policy_profile_pull_thread  - pull_monitoring_configuration to /xxxx/xxx/xxx/configuration_reader_service failed with unknown error 
Feb 12 01:12:20:768 [6780] 0 spooler: (Metric Plugin): Read probes from metric cfg - error, could not open metric cfg 

  • Robots(spooler) periodically checks with the CRS probe. Is a Pull mode.Default is every 4 mins
  • Every robot checks if there are new profile/policy created for it.
  • Robot does not access the mon_config_service probe or DB. CRS is the mediator
  • spooler computes the checksum of deployed profiles from (probe cfg files) and plugn-in metric files and send it to the CRS
  • This is true for every robot > 23.4.0

If the plugin_metric.cfg file was deleted for any reason or during any mcs related troubleshooting and not recreated this issue will occur

Can redeploy the same version of robot on top of existing via IM which should recreate the plugin_metric.cfg if missing and prevent the memory leak in this use case

Additional Information