Highly Frequent probe redeployment cause probe crash (probe remains deactivated)
search cancel

Highly Frequent probe redeployment cause probe crash (probe remains deactivated)

book

Article ID: 382104

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Very frequent probe deployments/redeployments are causing the probe to be found in crashed/ deactivated state. Why is this happening? 

 

 

Environment

DX UIM 23.4.*

Cause

The highly frequent deployment itself, does not cause this issue. The issue is only seen if together with the highly frequent deployments, there is a custom timeid probe which gets started also very frequently at the same time.

The reason is that the custom timed probes restart thread and the probe redeployment thread have some common parts.  Because of the frequent probe deployments this common part is triggered by both of them during the same time and it can cause memory corruptions and probe crash. 

Resolution

robot_update 23.4.2.2 fixes this issue. 

The upcoming GA Robot update will include this fix logic


Additional Information

In the fix added thread synchronisation between the common code, with this only one thread can handle common parts at a given point of time, with this the race condition to access the common code between the threads will be mitigated.

Attachments

robot_update-23.4.2.2.zip get_app