EcoStruxure IT forum
A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.
Posted: 2020-07-04 05:18 PM
This question was originally posted on DCIM Support by John Smith on 2018-05-08
I am getting this error in hs_err_pid680.log. Any thoughts?
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (nmap) failed to allocate 310378496 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system #
Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
# Out of Memory Error (os_linux.cpp:2627), pid=680, tid=0x00007f126d07e700
# JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build 1.8.0_102-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode Linux-amd64 compressed oops)
(CID:131336342)
Posted: 2020-07-04 05:18 PM
This comment was originally posted on DCIM Support by spezialist on 2018-05-08
Dear John Smith,
Under what circumstances did the above problem occur?
Did this issue occur while the Linux desktop DCE-client was running?
With respect.
(CID:131336438)
Posted: 2020-07-04 05:19 PM
This comment was originally posted on DCIM Support by John Smith on 2018-05-09
That issue was found in the DCE Server logs. Not the client. I only have windows clients installed.
(CID:131336840)
Posted: 2020-07-04 05:19 PM
This answer was originally posted on DCIM Support by spezialist on 2018-05-10
Dear John Smith,
Unfortunately, it's not easy to tell the root cause of the above JVM error on the DCE-server ☹️. You can, of course, point out the lack of RAM, but this is only true if your DCE-server has only 1GB of RAM (i.e., Basic DCE appliance), and the number of monitoring devices reaches up to a thousand.
Therefore, if this problem is not frequent and regular and does not involve a real lack of RAM, then I recommend simply updating your DCE-server to the latest version 7.5.0. This is a good practice, because judging by your log-file, the JVM version is old (latest version is 1.8.0_171), and updating the DCE-server you get also the latest version of JVM, which is very important for the normal operation of DCE software.
With respect.
(CID:131337109)
Posted: 2020-07-04 05:19 PM
This comment was originally posted on DCIM Support by John Smith on 2018-05-10
Thanks. The server has plenty of RAM, I think it is 16 or 20GB and 5 Cores. It should be flying!
(CID:131958416)
Posted: 2020-07-04 05:19 PM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.