Error Code details
Severity: Information 
Component: Cluster Server 
Fencing driver going into RUNNING state

When fencing starts, it configures the fencing driver. After the driver configuration completes, the fencing driver goes into the running state, and this message is displayed.


Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2012-02-03 08:34:10 PDT
Platform: Generic
Release: Generic

Do the following steps to find out the exact cause of the failure:

1. Check the resource consumption on the Indexer node for the file server or Web application.
The name of the Indexer node where the failure occurs is displayed on the Events page under the Origin column.
If the memory usage on the Indexer node is high and the available memory for idxwriter.exe to process the audit files is insufficient, it might cause a failure to update index with the audit data.
2. Run IndexCheckJob to check the data integrity of indexes.
1)      Open a command window on the Indexer node for the file server or Web application.
2)      Change the working directory to Data_Insight_Installation_Directory\bin.
3)      Run the following command:
configcli execute_job IndexCheckJob
4)      To check whether the job is complete, run the following command. The output of the command displays an asterisk (*) against the jobs that are currently running.
configcli list_jobs
5)      After the IndexCheckJob is complete, check the idxcheck.0.log file to see whether any index corruptions are reported.
3. Do the following steps:
1)      On the Indexer node, make sure that your current working directory is Data_Insight_Installation_Directory\bin.
2)      Run the following command to change the logging level for services:
configcli loglevel com.symc.matrix ALL
3)      Move the audit databases from Data_Directory\indexer\err folder to Data_Directory\inbox folder.
4)      Run IndexWriterJob by using the following command:
configcli execute_job IndexWriterJob
5)      If the audit database files are moved to the Data_Directory\indexer\err folder again, check the commd.0.0.log file to find out the reason for the failure to update index with the audit data. The commd.0.0.log file is in the Data_Insight_Installation_Directory\log folder.
6)      Contact Symantec Support if the audit database files continue to be moved to the Data_Directory\indexer\err folder.
Note: The default value for Data_Insight_Installation_Directory is C:\Program Files\Symantec\Data Insight. For Data_Directory, it is C:\DataInsight\Data. Thedefault directories can be changed during the installation. In that case, the values for Data_Insight_Installation_Directory and Data_Directory are changed accordingly.


Solution 2 Vote: [Useful] [Not useful]
Last Modified: 2012-01-07 03:34:49 PDT
Platform: Red Hat Enterprise Linux 5 (x86-32), Red Hat Enterprise Linux 5 (x86-64), Red Hat Enterprise Linux 5 (POWER)
Release: 5.1

This message is only for information. No action is required.


User solutions
No user solutions yet.


Read and accept Terms of Service