mon_config_service probe is spawning multiple process instances and consumes system memory usage
search cancel

mon_config_service probe is spawning multiple process instances and consumes system memory usage

book

Article ID: 258433

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We noticed that the mon_config_service probe spawns multiple process instances and consumes system memory usage.

How can we resolve this?

Environment

mon_config_service 20.33hf7

Cause

Corrupted mon_config_service instance

Resolution

1. Deactivate and delete the mon_config_service probe 

2. Kill any existing mon_config_service processes and delete/rename the probes/service/mon_config_service folder

3. Stop the Nimsoft Robot Watcher service and wait for 5 mins 

4. Start the Nimsoft Robot Watcher service and deploy the mon_config_service