NFA Reaper Service restarting

book

Article ID: 130139

calendar_today

Updated On:

Products

CA Network Flow Analysis (NetQos / NFA)

Issue/Introduction

Messages error:
Version=1
EventType=APPCRASH
EventTime=131974994841632795
ReportType=2
Consent=1
ReportIdentifier=3c6cc78e-4a82-11e9-80dc-005056866177
IntegratorReportIdentifier=3c6cc78d-4a82-11e9-80dc-005056866177
NsAppName=nfrtreaper.exe
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=nfrtreaper.exe
...
UI[8]=nfrtreaper.exe stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=E:\CA\NFA\netflow\bin\nfrtreaper.exe
...
AppName=nfrtreaper.exe
AppPath=E:\CA\NFA\netflow\bin\nfrtreaper.exe
NsPartner=windows
NsGroup=windows8

Cause

This problem is relates with Alert definition:
Flow alert on all interfaces causes Reaper service to stop and will not start and create application error until the alert has cleared from the harvester.trap_definitions table.

 

Environment

NFA 9.5

Resolution

Check on Harvester machine:
mysql
use harvester
select * from trap_definitions;

And on Console machine
mysql
use reporter
select * from trap_definitions;

Remove this Alert definition on NFA web page/Administration/Alerts Description "h interface" or use this command:

Check again on both NFA Console and Harverster machines:
select * from trap_definitions;

Note: You can force the remove with this command:
delete from trap_definitions where TrapName = 'nnnnn';  ---> Where nnnnn is the TrapName from select * from trap_definitions output
Run this command on Console and Harverster machines

Stop/Start the CA NFA Reaper Service