ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Processes probe on Linux terminates immediately after startup

book

Article ID: 226364

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The processes probe will not start no matter what version I use.  

 

The log only shows the folowing:

 


Aug  4 10:07:49:118 processes: ****************[ Starting ]****************
Aug  4 10:07:49:118 processes: processes 4.60, Aug 29 2017
Aug  4 10:07:49:118 processes: Nimsoft Corporation, Copyright @ 1998-2010
Aug  4 10:07:49:118 processes: nimSessionServer - port = 0
Aug  4 10:07:49:119 processes: sockCheckLocalPort: connect to port 48010 failed 111 (ok - its free)
Aug  4 10:07:49:119 processes: sockCheckLocalPort - close 4
Aug  4 10:07:49:119 processes: sockServer: next available port is 48010
Aug  4 10:07:49:119 processes: sockServer:0x787680:0.0.0.0/48010
Aug  4 10:07:49:119 processes: port=48010 PID=23148
Aug  4 10:07:49:119 processes: SREQUEST: port_register ->10.x.x.x/48000
Aug  4 10:07:49:119 processes: RREPLY: status=OK(0) <-10.x.x.x/48000  h=37 d=0
Aug  4 10:07:49:119 processes: sockClose:0x789700:10.x.x.x/34308
Aug  4 10:07:49:119 processes: SREQUEST: _close ->10.x.x.x/48000
Aug  4 10:07:50:120 [140084348446464] Controller: Max. restarts reached for probe 'processes' (command = processes)

Cause

corrupted file folder

Environment

Release : 20.3

Component : UIM - PROCESSES

Resolution

deleting probe  folder entirely and redeploying resolved issue - ultimate root cause not determined.