APM-Big directory heapdump
Hi,
I have this situation on AppManager, the wrapper log send this message:
ERROR | wrapper | 2018/05/11 17:43:26 | JVM exited unexpectedly.
STATUS | wrapper | 2018/05/11 17:43:33 | Launching a JVM...
INFO | jvm 2 | 2018/05/11 17:43:42 | WrapperManager: Initializing...
WARN | jvm 2 | 2018/05/11 17:43:51 | Not able to connect with the PgSql Database
WARN | jvm 2 | 2018/05/11 17:43:53 | Not able to connect with the PgSql Database
WARN | jvm 2 | 2018/05/11 17:43:55 | Not able to connect with the PgSql Database
WARN | jvm 2 | 2018/05/11 17:43:57 | Not able to connect with the PgSql Database
STATUS | wrapper | 2018/05/11 17:44:14 | on_exit trigger matched. Restarting the JVM. (Exit code: 1)
STATUS | wrapper | 2018/05/11 17:44:19 | Launching a JVM...
INFO | jvm 3 | 2018/05/11 17:44:19 | WrapperManager: Initializing...
WARN | jvm 3 | 2018/05/11 17:44:28 | Not able to connect with the PgSql Database
WARN | jvm 3 | 2018/05/11 17:44:30 | Not able to connect with the PgSql Database
WARN | jvm 3 | 2018/05/11 17:44:32 | Not able to connect with the PgSql Database
WARN | jvm 3 | 2018/05/11 17:44:34 | Not able to connect with the PgSql Database
STATUS | wrapper | 2018/05/11 17:44:49 | on_exit trigger matched. Restarting the JVM. (Exit code: 1)
STATUS | wrapper | 2018/05/11 17:44:55 | Launching a JVM...
INFO | jvm 4 | 2018/05/11 17:44:55 | WrapperManager: Initializing...
WARN | jvm 4 | 2018/05/11 17:45:03 | Not able to connect with the PgSql Database
WARN | jvm 4 | 2018/05/11 17:45:05 | Not able to connect with the PgSql Database
WARN | jvm 4 | 2018/05/11 17:45:07 | Not able to connect with the PgSql Database
WARN | jvm 4 | 2018/05/11 17:45:09 | Not able to connect with the PgSql Database
STATUS | wrapper | 2018/05/11 17:45:25 | on_exit trigger matched. Restarting the JVM. (Exit code: 1)
STATUS | wrapper | 2018/05/11 17:45:30 | Launching a JVM...
INFO | jvm 5 | 2018/05/11 17:45:30 | WrapperManager: Initializing...
WARN | jvm 5 | 2018/05/11 17:45:39 | Not able to connect with the PgSql Database
WARN | jvm 5 | 2018/05/11 17:45:41 | Not able to connect with the PgSql Database
WARN | jvm 5 | 2018/05/11 17:45:43 | Not able to connect with the PgSql Database
WARN | jvm 5 | 2018/05/11 17:45:45 | Not able to connect with the PgSql Database
STATUS | wrapper | 2018/05/11 17:46:00 | on_exit trigger matched. Restarting the JVM. (Exit code: 1)
FATAL | wrapper | 2018/05/11 17:46:01 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
FATAL | wrapper | 2018/05/11 17:46:01 | There may be a configuration problem: please check the logs.
And when I tried to start the process of Central, send this other:
INFO | jvm 1 | 2018/05/14 09:37:32 | DiskSpaceMonitor :: disk space is too low [Shutting down server]..free up disk and start again
INFO | jvm 1 | 2018/05/14 09:37:32 | System halted
When I search on the directory of installation the unit E: had only 500MB I delete the reciclye byn and backup of logs and now I have 5GB free of space but the directory
E:\ManageEngine\OpManagerProbe\AppManager\working\heapdump size is
33.5GB and I don't know if I can delete the heapdump_Mon_dd_yyyy_hh_mm_#.bin files or this a issue with the appliction.
Thanks and Regards!
Angela M.