INFO | jvm 1 | 2021/06/25 16:08:51 | [2021-06-25T16:08:51,108][INFO][o.e.n.Node][int_Server-Name] started INFO | jvm 1 | 2021/06/25 16:08:51 | [2021-06-25T16:08:51,108][INFO][c.z.z.d.e.ESWrapperManager] ES started in : 11.4s INFO | jvm 1 | 2021/06/25 16:08:52 | [2021-06-25T16:08:51,967][INFO][c.f.s.c.IndexBaseConfigurationRepository] Node 'int_Server-Name' initialized |
2. If Elasticsearch is running, the steps below will manually start the ES:
- Open the Command Prompt with admin privileges.
- Navigate to <dir>:\ManageEngine\elasticSearch\ES\bin and execute stopES.bat to stop the engine.
- After a couple of minutes, execute startES.bat to start the engine.
3. Open the <dir>:\ManageEngine\elasticsearch\ES\logs\wrapper.log file. Carry out the following steps according to the traces found.
- Out of memory or JVM heap memory:
- Stop ES by executing the stopES.bat file located in the <dir>:\ManageEngine\elasticsearch\ES\bin folder.
- Open the <dir>:\ManageEngine\elasticsearch\ES\config\es-additional-wrapper.conf file.
- Increase the Initial Java Heap Size and Maximum Java Heap Size to one-third of the server's RAM size. For example, if the server has 16GB, you can assign up to 4GB as the heap space as a best practice.
Note: Both Initial Java Heap Size and Maximum Java Heap Size should have the same value.b. Incorrect read/write permissions (e.g., location not found):
- Stop ES by executing the stopES.bat file located in the <dir>:\ManageEngine\elasticsearch\ES\bin folder.Check if the Service Account has read/write access to the ES storage location.
- Restart ES after carrying out the relevant process.