EMS probe folder is increasing in size and EMS probe is not starting
search cancel

EMS probe folder is increasing in size and EMS probe is not starting


Article ID: 245122


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


The ems folder is occupying a huge space in the nimsoft folder. MDMP files are getting created.

The ems probe is red and not starting




Release : 20.4

Component :


hs_err_pid indicated that ems is running out of memory

# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 267936 bytes for Chunk::new
# Possible reasons:
#   The system is out of physical RAM or swap space
#   The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
# Possible solutions:
#   Reduce memory load on the system
#   Increase physical memory or swap space
#   Check if swap backing store is full
#   Decrease Java heap size (-Xmx/-Xms)
#   Decrease number of Java threads
#   Decrease Java thread stack sizes (-Xss)
#   Set larger code cache with -XX:ReservedCodeCacheSize=
#   JVM is running with Unscaled Compressed Oops mode in which the Java heap is
#     placed in the first 4GB address space. The Java Heap base address is the
#     maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
#     to set the Java Heap base and to place the Java Heap above 4GB virtual address.
# This output file may be truncated or incomplete.
#  Out of Memory Error (allocation.cpp:389), pid=10828, tid=0x0000000000000360


The possible reasons and solutions are also specified in the error message in hs_err_pid as mentioned above.

- check if you have enough physical memory or swap space on your server.

- access raw configure of ems probe, then startup then opt then increase java_mem_init to 1024 and java_mem_max to 2048.