Error Code details
V-378-1312-301
Severity: Error 
Component: Data Insight 
Message:
Error generating audit log data for extracts <extract_ids>. Input files <file list> moved to data/collector/err folder.
Description:

This message is displayed in the Data Insight Events page on the Data Insight Management Console when the Collector component of Data Insight fails to generate the audit database. The possible causes for this error are:

  • Insufficient memory to process the intermediate databases (Fpolicy, Celerra, or Winnas sqlite databases)
     
  • Insufficient disk space to generate the audit databases

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2014-10-02 21:26:52 PST
Platform: Windows Server 2003 (x86-64), Windows Server 2003 (IA-64), Windows Server 2003 (x86-32), Windows Server 2008 (x86-64), Windows Server 2008 (IA-64), Windows Server 2008 (x86-32), Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016
Release: Generic
Content:
  1. Check the resource consumption on the Collector node for the file server. The name of the Collector node where the failure occurs is displayed in the Events page under the Origin column. The Collector node fails to generate audit log data when either of the following happens:
  • The memory usage on the Collector node is high and the memory available for collector.exe to process the scan files is insufficient.
     
  • The disk space on the Collector node is insufficient.
  1. Free up the resources and do the following steps:
    1. Open a command window.
       
    2. Change the working directory to Data_Insight_Installation_Directory\bin.
       
    3. Change the logging level for the services on the Collector node and the Management Server. Run the following commands:
      • On the Collector Node: configcli loglevel com.symc.matrix ALL
         
      • On the Management Server: configcli backend_loglevel node_id collector FINE

where node_id is the ID of the Collector node and can be obtained in the following ways:
 

  • For Symantec Data Insight 2.5, run configdb -p -T node
     
  • For earlier versions, run configdb –N
     

It takes about one minute for the configuration changes to take effect on the Collector node.

  1. On the Collector node, move the input databases from Data_Directory\collector\err to Data_Directory\collector. Run the following command to run CollectorJob:

              configcli execute_job CollectorJob

  1. If the input files are moved to the collector\err folder again, find the collector.log file in the Data_Insight_Installation_Directory\log folder. The reason for the failure to generate audit log data might be indicated in the collector.log file.
     
  2. If the input files for the collector continue to be moved to the collector\err folder, contact Symantec Support.

Note: The default value for Data_Insight_Installation_Directory is C:\Program Files\Symantec\DataInsight. For Data_Directory, it is C:\DataInsight\Data. The default directories can be changed during the installation. In that case, the values for Data_Insight_Installation_Directory and Data_Directory are changed accordingly.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service