dirscan probe crash/core dump when stopped or restarted

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The dirscan probe appears to be crashing whenever it is deactivated or restarted.

On Windows, crash information similar to the following is generated:

Faulting application name: dirscan.exe, version: 0.0.0.0, time stamp: 0x68d412f4
Faulting module name: ntdll.dll, version: 10.0.17763.6414, time stamp: 0xd2a47020
Exception code: 0xc0000374
Fault offset: 0x00000000000fb199
Faulting process id: 0x2160
Faulting application start time: 0x01dc948965c1e412
Faulting application path: C:\Program Files (x86)\Nimsoft\probes\system\dirscan\dirscan.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 70d3e1e7-ab03-4c1f-92ec-15219f79fcff
Faulting package full name: 
Faulting package-relative application ID: 

On Linux, messages similar to the following are seen in /var/log/messages:

 

 Process 3531 (dirscan) of user 0 dumped core.#012#012Stack trace of thread 3531:#012#0  0x00007f8b00a8b52c __pthread_kill_implementation (libc.so.6 + 0x8b52c)#012#1  0x00007f8b00a3e686 raise (libc.so.6 + 0x3e686)#012#2  0x00007f8b00a28833 abort (libc.so.6 + 0x28833)#012#3  0x00007f8b00a29170 __libc_message.cold (libc.so.6 + 0x29170)#012#4  0x00007f8b00a955d7 malloc_printerr (libc.so.6 + 0x955d7)#012#5  0x00007f8b00a96e8c _int_free (libc.so.6 + 0x96e8c)#012#6  0x00007f8b00a99915 free (libc.so.6 + 0x99915)#012#7  0x0000000000487671 n/a (/opt/nimsoft/probes/system/dirscan/dirscan + 0x87671)#012#8  0x00000000004879f3 n/a (/opt/nimsoft/probes/system/dirscan/dirscan + 0x879f3)#012#9  0x00000000004a3180 n/a (/opt/nimsoft/probes/system/dirscan/dirscan + 0xa3180)#012#10 0x00007f8b00a295d0 __libc_start_call_main (libc.so.6 + 0x295d0)#012#11 0x00007f8b00a29680 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x29680)#012#12 0x00000000004874d9 n/a (/opt/nimsoft/probes/system/dirscan/dirscan + 0x874d9)#012ELF object binary architecture: AMD x86-64

 

 

 

Environment

DX UIM - Any Version
dirscan probe - 4.03

Cause

defect

Resolution

Engineering is investigating this as a defect.  It is expected to be resolved in the next version of dirscan after 4.03.