NAS probe is red and throwing Max. Restarts error
search cancel

NAS probe is red and throwing Max. Restarts error

book

Article ID: 270701

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

NAS probe isn't working in UIM.

The nas probe configuration seemed to have some form of corruption which was causing this error and therefore Max. restarts and the nas turned red and stopped working.

Jul 29 15:25:07:648 [6108] 3 nas: nimMD5CheckSum- 842d65bb436dc5001262b269cbb18ef1 
Jul 29 15:25:07:648 [6108] 3 nas: [0xAC5EC660] Database provider is 'SQLOLEDB', database '<database_name>' 
Jul 29 15:25:07:692 [6108] 0 nas: nisInitialize: NOT enabling batch mode 
Jul 29 15:25:07:692 [6108] 3 nas: [0xAC801230] Database provider is 'sqlite3', database 'nisQueue.db' 
Jul 29 15:25:07:699 [6108] 0 nas: _nisQueueDatabaseCreate: Dropped old NIS_QUEUE table from nisqueue.db 
Jul 29 15:25:07:708 [5416] 3 nas: [0xAC800C40] Database provider is 'sqlite3', database 'nisQueue.db' 
Jul 29 15:25:07:708 [6108] 4 nas: CONNECT: 0000004AA7722B40(25920) ##.###.##.###/51252->##.###.##.###/48000 
Jul 29 15:25:07:708 [6108] 5 nas: SREQUEST: probe_verify ->##.###.##.###/48000 
Jul 29 15:25:07:838 [6108] 5 nas: RREPLY: status=OK(0) <-##.###.##.###/48000  h=37 d=0 fd=25920 
Jul 29 15:25:07:838 [6108] 5 nas: SREQUEST: _close ->##.###.##.###/48000 
Jul 29 15:25:07:839 [6108] 4 nas: CONNECT: 0000004AA7760960(26100) ##.###.##.###/51261->##.###.##.###/48000 
Jul 29 15:25:07:839 [6108] 5 nas: SREQUEST: nametoip ->##.###.##.###/48000 
Jul 29 15:25:08:010 [7680] Controller: Max. restarts reached for probe 'nas' (command = nas.exe)

Environment

  • Release: DX UIM 20.3
  • OS: Windows 2016
  • nas 9.37

Cause

  • nas local files, database corruption

Resolution

  • Reinstalled the nas version 9.37 and it started working and continued to work without issue.
  • In the process of examining the nas and alarm_enrichment configuration, it was noticed that the alarm Subjects were not correct, but they were ok/working for now. The Subjects defined appear to be from a past version of UIM where Subjects were changed due to the implementation of the ems probe. This was a known issue at the time, it's an old issue, but there is a KB that provides the solution:

    How to switch back from using EMS to using NAS again