Hi Manuel, from your top screenshot we can see that you only have 3.5 GB of physical RAM and your 5GB swap space is full - so your _machine_ is out of memory.
If possible, add more physical memory. If that's not possible, increase the swap space - but you will suffer _severe_ performance degradation in this setup. Another thought: Why do the java processes run as root? I suspect those are the DSpace processes? This is *really dangerous*, setup another non-privileged user for it! Regards, Holger On 10.11.2015 23:57, Manuel Hidalgo wrote: > Hi Luiz, > Attached display of commad top > > This is our /etc/profile > > export CATALINA_HOME="/datadrive/tomcat" > export CATALINA_BASE="/datadrive/tomcat" > export JAVA_HOME="/usr/java/jdk1.8.0_40" > export JRE_HOME="/usr/java/jdk1.8.0_40" > export JAVA_OPTS="-Xms1024m –Xmx2048m -XX:MaxPermSize=128m > -Dfile.encoding=UTF-8 > -Djava.awt.headless=true" > export M2_HOME="/usr/maven" > export MAVEN_HOME="/usr/maven" > export ANT_HOME="/usr/ant" > export PATH=$PATH:$JAVA_HOME/bin:$ANT_HOME/bin:$M2_HOME/bin:$MAVEN_HOME/bin > > > 2015-11-10 16:35 GMT-06:00 Luiz dos Santos <[email protected] > <mailto:[email protected]>>: > > Hi Manuel, > > Did you tried improve the -XX:MaxPermSize=128m? When you user the top? > What is the usage of you memory? Do you check if there is bot making high > traffic in you DSpace? > > Thanks > Luiz > > On Tue, Nov 10, 2015 at 5:23 PM, Tim Donohue <[email protected] > <mailto:[email protected]>> wrote: > > Hi Manuel, > > At a basic level, it's hard to say whether you'd either need to > increase > your memory, or whether a particular *setting or process* is causing > the > Out Of Memory Error. Unfortunately, the logs you sent along are not > enough information for us to be able to tell what exactly is going on > in > your DSpace site. > > That being said, here are the performance tuning recommendations for > DSpace with regards to Out of Memory errors > https://wiki.duraspace.org/display/DSDOC5x/Performance+Tuning+DSpace > > If you need additional help, you would need to send more information > to > this mailing list (dspace-tech). For example: > * What version of DSpace are you running? If you are on 5.x, I'd > recommend upgrading immediately to 5.4 as it includes memory related > enhancements > * How much RAM do you current have? > * How much Java Heap memory have you allocated to DSpace/Tomcat? (See > the Performance Tuning settings above) > * Is there anything else running on this server alongside DSpace? > * How frequently are you hitting this out-of-memory error after > restarting DSpace? Multiple times a day? Daily? Weekly? > * Are there particular activities which cause this out-of-memory error > to occur? Are you simply browsing/searching? Is there another process > running at the time? > > At a basic level, if you are hitting this error frequently, it's > likely > your DSpace needs more memory allocated towards it. If you have > already > allocated all of your system's RAM, that may mean adding more RAM. > But, > if you have not, you might just be able to update the settings for > "Xms/Xmx" as noted in the "performance tuning" docs above. You also > might consider upgrading to DSpace 5.4 which did include some > memory-related fixes (specifically for browsing/searching and > reindexing > content in Solr). > > So, if you are unable to figure out the best route, you are welcome to > send more information to this mailing list. I'd encourage you to just > email the DSpace Tech Support list ([email protected] > <mailto:[email protected]>), as it's the best place to get > help for these sorts of issues. > > Good luck, > > Tim > > > On 11/10/2015 3:59 PM, Manuel Hidalgo wrote: >> >> Dear all, >> >> >> We have problems with our DSPACE Server in Centos, the logs >> display this information, we need to increace the RAM? >> >> >> >> Log Tomcat: >> >> >> # >> >> # There is insufficient memory for the Java Runtime Environment >> to >> continue. >> >> # Native memory allocation (mmap) failed to map 128974848 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:2673), pid=1616, >> tid=140545783281408 >> >> # >> >> # JRE version: Java(TM) SE Runtime Environment (8.0_40-b25) >> (build >> 1.8.0_40-b25) >> >> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.40-b25 mixed >> mode >> linux-amd64 compressed oops) >> >> # Failed to write core dump. Core dumps have been disabled. To >> enable core dumping, try "ulimit -c unlimited" before starting >> Java again >> >> # >> >> >> --------------- T H R E A D --------------- >> >> >> Current thread (0x00007fd370072800): VMThread [stack: >> 0x00007fd35d6cb000,0x00007fd35d7cc000] [id=1620] >> >> >> Stack: [0x00007fd35d6cb000,0x00007fd35d7cc000], >> sp=0x00007fd35d7ca1e0, free space=1020k >> >> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, >> C=native code) >> >> V [libjvm.so+0xaaca9a] VMError::report_and_die()+0x2ba >> >> V [libjvm.so+0x4f333b] report_vm_out_of_memory(char const*, >> int, >> unsigned long, VMErrorType, char const*)+0x8b >> >> V [libjvm.so+0x90e8c3] os::Linux::commit_memory_impl(char*, >> unsigned long, bool)+0x103 >> >> V [libjvm.so+0x90ee19] os::pd_commit_memory(char*, unsigned >> long, unsigned long, bool)+0x29 >> >> V [libjvm.so+0x90877a] os::commit_memory(char*, unsigned long, >> unsigned long, bool)+0x2a >> >> V [libjvm.so+0x97bbc3] PSVirtualSpace::expand_by(unsigned >> long)+0x53 >> >> V [libjvm.so+0x97cfc8] PSYoungGen::resize_generation(unsigned >> long, unsigned long)+0xf8 >> >> V [libjvm.so+0x97c122] PSYoungGen::resize(unsigned long, >> unsigned long)+0x22 >> >> V [libjvm.so+0x9793fb] PSScavenge::invoke_no_policy()+0xf7b >> >> V [libjvm.so+0x979b81] PSScavenge::invoke()+0x41 >> >> V [libjvm.so+0x932150] >> ParallelScavengeHeap::failed_mem_allocate(unsigned long)+0x70 >> >> V [libjvm.so+0xaae2d7] >> VM_ParallelGCFailedAllocation::doit()+0x97 >> >> V [libjvm.so+0xab5ac5] VM_Operation::evaluate()+0x55 >> >> V [libjvm.so+0xab3e9a] >> VMThread::evaluate_operation(VM_Operation*)+0xba >> >> V [libjvm.so+0xab421e] VMThread::loop()+0x1ce >> >> V [libjvm.so+0xab4690] VMThread::run()+0x70 >> >> V [libjvm.so+0x910ee8] java_start(Thread*)+0x108 >> >> >> VM_Operation (0x00007fd32fdfd670): ParallelGCFailedAllocation, >> mode: safepoint, requested by thread 0x00007fd328003000 >> >> >> >> --------------- P R O C E S S --------------- >> >> >> Java Threads: ( => current thread ) >> >> 0x00007fd328003000 JavaThread "localhost-startStop-1" daemon >> [_thread_blocked, id=1630, >> stack(0x00007fd32fcff000,0x00007fd32fe00000)] >> >> 0x00007fd3703a1800 JavaThread "Catalina-startStop-1" daemon >> [_thread_blocked, id=1629, >> stack(0x00007fd35c07d000,0x00007fd35c17e000)] >> >> 0x00007fd3702f2000 JavaThread "GC Daemon" daemon >> [_thread_blocked, id=1628, >> stack(0x00007fd35c5f0000,0x00007fd35c6f1000)] >> >> 0x00007fd3700ab000 JavaThread "Service Thread" daemon >> [_thread_blocked, id=1626, >> stack(0x00007fd35d0c5000,0x00007fd35d1c6000)] >> >> 0x00007fd3700a8800 JavaThread "C1 CompilerThread1" daemon >> [_thread_blocked, id=1625, >> stack(0x00007fd35d1c6000,0x00007fd35d2c7000)] >> >> 0x00007fd3700a5800 JavaThread "C2 CompilerThread0" daemon >> [_thread_in_native, id=1624, >> stack(0x00007fd35d2c7000,0x00007fd35d3c8000)] >> >> 0x00007fd3700a3800 JavaThread "Signal Dispatcher" daemon >> [_thread_blocked, id=1623, >> stack(0x00007fd35d3c8000,0x00007fd35d4c9000)] >> >> 0x00007fd370079800 JavaThread "Finalizer" daemon >> [_thread_blocked, id=1622, >> stack(0x00007fd35d4c9000,0x00007fd35d5ca000)] >> >> 0x00007fd370077800 JavaThread "Reference Handler" daemon >> [_thread_blocked, id=1621, >> stack(0x00007fd35d5ca000,0x00007fd35d6cb000)] >> >> 0x00007fd370009000 JavaThread "main" [_thread_blocked, id=1617, >> stack(0x00007fd376904000,0x00007fd376a05000)] >> >> >> Other Threads: >> >> =>0x00007fd370072800 VMThread [stack: >> 0x00007fd35d6cb000,0x00007fd35d7cc000] [id=1620] >> >> 0x00007fd3700b2000 WatcherThread [stack: >> 0x00007fd35cfc4000,0x00007fd35d0c5000] [id=1627] >> >> >> VM state:at safepoint (normal execution) >> >> >> VM Mutex/Monitor currently owned by a thread: >> ([mutex/lock_event]) >> >> [0x00007fd3700063b0] Threads_lock - owner thread: >> 0x00007fd370072800 >> >> [0x00007fd3700068b0] Heap_lock - owner thread: 0x00007fd328003000 >> >> >> Heap: >> >> PSYoungGen total 125440K, used 12783K [0x00000000ee100000, >> 0x00000000f6a00000, 0x0000000100000000) >> >> eden space 112640K, 0% used >> [0x00000000ee100000,0x00000000ee100000,0x00000000f4f00000) >> >> from space 12800K, 99% used >> [0x00000000f4f00000,0x00000000f5b7bc98,0x00000000f5b80000) >> >> to space 10752K, 0% used >> [0x00000000f5b80000,0x00000000f5b80000,0x00000000f6600000) >> >> ParOldGen total 36864K, used 30701K [0x00000000ca200000, >> 0x00000000cc600000, 0x00000000ee100000) >> >> object space 36864K, 83% used >> [0x00000000ca200000,0x00000000cbffb660,0x00000000cc600000) >> >> Metaspace used 12882K, capacity 13134K, committed 13312K, >> reserved 1060864K >> >> class space used 1394K, capacity 1461K, committed 1536K, >> reserved 1048576K >> >> >> Card table byte_map: [0x00007fd360a90000,0x00007fd360c40000] >> byte_map_base: 0x00007fd36043f000 >> >> >> Marking Bits: (ParMarkBitMap*) 0x00007fd375dd06c0 >> >> Begin Bits: [0x00007fd35ec7e000, 0x00007fd35f9f6000) >> >> End Bits: [0x00007fd35f9f6000, 0x00007fd36076e000) >> >> >> Polling page: 0x00007fd376a11000 >> >> >> CodeCache: size=245760Kb used=6178Kb max_used=6178Kb >> free=239581Kb >> >> bounds [0x00007fd361000000, 0x00007fd361610000, >> 0x00007fd370000000] >> >> total_blobs=1873 nmethods=1533 adapters=254 >> >> compilation: enabled >> >> >> Compilation events (10 events): >> >> Event: 18.392 Thread 0x00007fd3700a8800 1570 3 >> java.util.Hashtable::<init> (8 bytes) >> >> Event: 18.393 Thread 0x00007fd3700a8800 nmethod 1570 >> 0x00007fd3615f6b50 code [0x00007fd3615f6ce0, 0x00007fd3615f6e68] >> >> Event: 18.437 Thread 0x00007fd3700a8800 1571 3 >> sun.security.util.ManifestEntryVerifier::<init> (60 bytes) >> >> Event: 18.441 Thread 0x00007fd3700a8800 nmethod 1571 >> 0x00007fd3615f5e90 code [0x00007fd3615f6080, 0x00007fd3615f67a8] >> >> Event: 18.441 Thread 0x00007fd3700a8800 1572 3 >> org.apache.catalina.deploy.WebXml::mergeResourceMap (167 bytes) >> >> Event: 18.442 Thread 0x00007fd3700a8800 nmethod 1572 >> 0x00007fd361607110 code [0x00007fd3616073e0, 0x00007fd3616089b8] >> >> Event: 18.442 Thread 0x00007fd3700a8800 1573 1 >> org.apache.catalina.deploy.SessionConfig::getSessionTrackingModes >> (5 bytes) >> >> Event: 18.443 Thread 0x00007fd3700a8800 nmethod 1573 >> 0x00007fd3615f5bd0 code [0x00007fd3615f5d20, 0x00007fd3615f5e30] >> >> Event: 18.833 Thread 0x00007fd3700a8800 1575 3 >> java.io.FilterInputStream::close (8 bytes) >> >> Event: 18.837 Thread 0x00007fd3700a8800 nmethod 1575 >> 0x00007fd3615f5790 code [0x00007fd3615f5900, 0x00007fd3615f5b28] >> >> >> GC Heap History (10 events): >> >> Event: 7.524 GC heap after >> >> Heap after GC invocations=2 (full 0): >> >> PSYoungGen total 30720K, used 2026K [0x00000000ee100000, >> 0x00000000f0100000, 0x0000000100000000) >> >> eden space 28672K, 0% used >> [0x00000000ee100000,0x00000000ee100000,0x00000000efd00000) >> >> from space 2048K, 98% used >> [0x00000000eff00000,0x00000000f00fa820,0x00000000f0100000) >> >> to space 2048K, 0% used >> [0x00000000efd00000,0x00000000efd00000,0x00000000eff00000) >> >> ParOldGen total 36864K, used 4890K [0x00000000ca200000, >> 0x00000000cc600000, 0x00000000ee100000) >> >> object space 36864K, 13% used >> [0x00000000ca200000,0x00000000ca6c6858,0x00000000cc600000) >> >> Metaspace used 12065K, capacity 12290K, committed 12416K, >> reserved 1060864K >> >> class space used 1335K, capacity 1394K, committed 1408K, >> reserved 1048576K >> >> } >> >> Event: 12.944 GC heap before >> >> {Heap before GC invocations=3 (full 0): >> >> PSYoungGen total 30720K, used 30698K [0x00000000ee100000, >> 0x00000000f0100000, 0x0000000100000000) >> >> eden space 28672K, 100% used >> [0x00000000ee100000,0x00000000efd00000,0x00000000efd00000) >> >> from space 2048K, 98% used >> [0x00000000eff00000,0x00000000f00fa820,0x00000000f0100000) >> >> to space 2048K, 0% used >> [0x00000000efd00000,0x00000000efd00000,0x00000000eff00000) >> >> ParOldGen total 36864K, used 4890K [0x00000000ca200000, >> 0x00000000cc600000, 0x00000000ee100000) >> >> object space 36864K, 13% used >> [0x00000000ca200000,0x00000000ca6c6858,0x00000000cc600000) >> >> Metaspace used 12683K, capacity 12910K, committed 13312K, >> reserved 1060864K >> >> class space used 1388K, capacity 1429K, committed 1536K, >> reserved 1048576K >> >> Event: 12.989 GC heap after >> >> Heap after GC invocations=3 (full 0): >> >> PSYoungGen total 30720K, used 2025K [0x00000000ee100000, >> 0x00000000f1d00000, 0x0000000100000000) >> >> eden space 28672K, 0% used >> [0x00000000ee100000,0x00000000ee100000,0x00000000efd00000) >> >> from space 2048K, 98% used >> [0x00000000efd00000,0x00000000efefa460,0x00000000eff00000) >> >> to space 2048K, 0% used >> [0x00000000f1b00000,0x00000000f1b00000,0x00000000f1d00000) >> >> ParOldGen total 36864K, used 6681K [0x00000000ca200000, >> 0x00000000cc600000, 0x00000000ee100000) >> >> object space 36864K, 18% used >> [0x00000000ca200000,0x00000000ca8864d0,0x00000000cc600000) >> >> Metaspace used 12683K, capacity 12910K, committed 13312K, >> reserved 1060864K >> >> class space used 1388K, capacity 1429K, committed 1536K, >> reserved 1048576K >> >> } >> >> Event: 14.540 GC heap before >> >> {Heap before GC invocations=4 (full 0): >> >> >> >> >> -- >> <http://www.sidalc.net/> >> >> <http://www.sidalc.net> >> >> -- >> You received this message because you are subscribed to the Google >> Groups "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, >> send >> an email to [email protected] >> <mailto:[email protected]>. >> To post to this group, send email to [email protected] >> <mailto:[email protected]>. >> Visit this group at http://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. > > -- > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > > -- > You received this message because you are subscribed to the Google > Groups "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > <http://www.sidalc.net/> > > <http://www.sidalc.net> > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email > to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. -- Dipl.-Inf. Holger Mickler Technische Universität Dresden Center for Information Services and High Performance Computing (ZIH) 01062 Dresden Germany Office: Willers-Bau (WIL) A109 Tel.: +49 (351) 463-37903 Fax: +49 (351) 463-37773 E-Mail: [email protected] OTR-Fingerprint: 3E567E9B 3B57F121 58B3C4EC 51E44C6B C3DCC191 -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
