Follow

Capture Processing Engine Debug/Error Logs

Created by: Brendan Bone
Created date:
Last Updated date:

Introduction: Sometimes, diagnosing an issue with processing can be difficult and may necessitate reviewing debug data.  The following will allow you to capture debug output from the Processing Engine which can then be reviewed by Accessdata Support.  This can be used with any Accessdata product that makes use of the Accessdata Processing Engine.

Procedure:

  1. Confirm there are no active processing jobs
  2. Open your case/project folder
  3. Create an empty file named debuglogs.txt in that case folder
  4. Start a new processing job to reproduce the reported issue

Note:

  • Debug Logs must be enabled on a case-by-case basis.
  • The existence of the debuglogs.txt file is an indicator to trigger additional logging. The additional logs are actually stored in the "Jobs" folder and its subfolders within the case folder.
  • After you have collected the desired logs, you should delete the debuglogs.txt file to prevent the logs from growing too large.
  • Some logs may be in compressed format and cannot be viewed until decompressed. Add an extension for a compressed file format (e.g. append ".gz" or ".7z") and decompress (e.g. using 7zip).
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    Tony Oakes

    The issue appears to be when FTK is performing the database inserts. FTK hangs. I tried to attach the logs but it isn't working through this interface.
    I have the log data but need to be able to get that to you.
    The debuglogs.txt file isn't generating anything.

Powered by Zendesk