Error 500 when loading the GUI
- Open the <dir>:\ManageEngine\elasticsearch\ES\logs\wrapper.log file and check the status of Elasticsearch (ES). The log traces below are for reference.
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.
If you are still seeing Error 500, get in touch with our technical support team.
New to ADSelfService Plus?
Related Articles
What to do if the component inside Log360 is not loading?
Troubleshooting Steps: Please ensure that the connection is proper, if in case of a connection issue, the components will not load within Log360. Local Integration: It is less likely to be a connection issue, in case of local integration, because ...GUI displays a blank page after login
Before beginning the troubleshooting process: Clear the browser cache and cookies. Open in the browser's incognito mode. Check in a different browser. Log in from a different machine. Troubleshooting steps have been provided below: If EventLog ...Error: Low memory detected on Log360's Elasticsearch
Issue description When using build version 12411 and below, you may get this in-product critical notification: Low memory detected on Log360's elasticsearch, increase the memory to at least X GB. This article explains the error message and what ...Slow GUI navigation
Verify that the prerequisites and system requirements for EventLog Analyzer are met. Under the Search tab, you will find all the logs collected in a working day. Use this number to calculate the events per second (EPS) manually. Use our tuning guide ...Error: A network capture driver is not available in the Log Receiver
Issue description Users may encounter the message "Network capture driver not available" in the Log Receiver. Network capture drivers are essential for EventLog Analyzer to capture and process real-time network logs from various sources. When a ...