Error Message

Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Date: 9/27/2024 7:14:35 PM
Event ID: 41312
Task Category: Elasticsearch Indexing Engine
Level: Error
Keywords: Classic
User: N/A
Computer: 
Description:
The Elasticsearch Indexing Engine could not complete all the required startup routines: Failed to start Elasticsearch JVM. Service will be stopped.

V-437-41312

-----

Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Date: 9/27/2024 7:14:35 PM
Event ID: 41293
Task Category: Index Admin Service
Level: Error
Keywords: Classic
User: N/A
Computer: 
Description:
An unexpected error has occurred. Error Summary: Indexing Service start up error
Error Details: Fatal error in Indexing Service child process EV Indexing Engine Elasticsearch. Further error information:
Error while waiting to achieve the requested state Running.
Reference: ServiceBaseEx::Run
Stack Trace: at KVS.EnterpriseVault.ProcessManagement.ChildProcessManager.StartChildProcesses()
at Symantec.EnterpriseVault.Indexing.Admin.StateManager.StartChildProcesses()
at Symantec.EnterpriseVault.Indexing.Admin.IndexAdminService.OnPerformStartup(Boolean HotRestart)
at KVS.EnterpriseVault.Common.ServiceBaseEx.Run()

V-437-41293

-----

Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Date: 9/27/2024 7:14:43 PM
Event ID: 41298
Task Category: Index Admin Service
Level: Information
Keywords: Classic
User: N/A
Computer: 
Description:
The Indexing Service has stopped (14.2.2.1434).

V-437-41298

----

A trace of the EVIndexingEngineElasticsearch process shows a similar error listed below:

EVServer1:9556>    EV-L    {ElasticsearchLogger} [o.e.e.NodeEnvironment] using [1] data paths, mounts [[INDEX (G:)]], net usable_space [80.1gb], net total_space [150.0gb], types [NTFS] 

EVServer2:7000>    EV-H    {ElasticsearchLogger} org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: failed to obtain node locks, tried [[E:\ElasticIndexFolderPath]] 

Note: EVServer2 is unable to obtain a lock on the Elasticsearch indexing folder path (E:\ElasticIndexFolderPath) 

This is due to the fact that both EVServer1 and EVServer2 have their indexing folder path set to the same path. (E:\Elastic)

This is not allowed in a Building Blocks scenario as server level folder paths must be unique. (Storage Queue, SMTP Holder, PST Migration, Server Cache, Index Metadata, Index Folder) etc .. 

Ensure that the Elasticsearch Index location on both Enterprise Vault Servers participating in Building Blocks are unique and do not overlap.