How to troubleshoot JVM Memory Error?
- Stop the ManageEngine EventLog Analyzer service.
- Navigate to <EventLog Analyzer home>/server/conf.
- Open the file wrapper.conf.
- Search for wrapper.java.maxmemory.
- Change the default value (1024) to wrapper.java.maxmemory=4096. (The value should not exceed 1/3rd of the overall server memory)
- Save the file and start the ManageEngine EventLog Analyzer service and observe the behavior.
New to ADSelfService Plus?
Related Articles
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] ...
What are the prerequisites for IIS Site Discovery and how to troubleshoot it?
Prerequisites: Administrator access for the remote IIS Server i.e., the credentials to access IIS Log files and the configuration file location are listed below: IIS configuration file location: C:\Windows\System32\inetsrv\config\ IIS log files ...
DAE service failure during startup
Open the <dir>:\ManageEngine\EventLog Analyzer\logs\wrapper.log file. Search for DAEService status in the wrapper file. If it hasn't been created, look for the serverout_yyyy-mm-dd.txt file from the same day in the logs folder. Check whether the ...
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 ...
Time delay in exporting reports
One of the main reasons for delay in report exports is the large volume of report entries. To reduce the report export time, we recommend you generate and export only the information needed. Select the exact time period and columns that are required ...