Tech Tip: NFA Reaper Service Dies Periodically

Document created by KahlilVThomas Employee on Aug 13, 2014Last modified by KahlilVThomas Employee on Aug 13, 2014
Version 2Show Document
  • View in full screen mode

NFA Reaper Service Dies Periodically

 

Descriprion:
The "CA NFA Reaper" service dies periodically on an NFA Harvester machine.  The ReaperInput directory is filled with files and using up disk space.  The file "RealTimeReaperErrors*.log" from the day that the problem occurred contains an error message similar to the following:


03:00:00 Severity 2 - b_test failure at d:\buildagent\work\nfa_913_production\include\nqMemoryMappedFile.h 50 because D:\NETQOS\netflow\datafiles\ReaperInput\1406789940-9995_0.tbn
03:00:00 Severity 2 - 32 The process cannot access the file because it is being used by another process.

 

Solution:


This error occurs when a 3rd-party process touches a file in the ReaperInput directory, and prevents the Reaper service itself from processing the file.  This can cause the Reaper service to die.

 

Problems like that are caused by software such as Real Time Antivirus scans, and Backup utilities.  Make sure that the ReaperInput and ReaperWork directories are excluded from being accessed by such utilities.

 

Sometimes, it might not be obvious which 3rd-party process is interfering with the Reaper service.  The timestamp of the error message in the RealTimeReaperErrors log might give us a clue.  Check the Windows Event Viewer for any messages that indicate that an AV Scan or a Backup procedure began just before the Reaper process died.  Also, check whether Windows has any Scheduled Tasks defined to run at the same time.  Once we find out which process is interfering with the Reaper service, prevent that process from accessing the ReaperInput and ReaperWork directories under \Netflow\datafiles

Attachments

    Outcomes