IT34945: LOGCOLLECT ENDS WITH ERROR='CANNOT ALLOCATE MEMORY' (ERRNO=12)

APAR status

• Closed as program error.

Error description

• If the IBM Spectrum Protect Plus user interface (UI) is not
  working, command logcollect needs to be used to collect log
  bundle. When running the following command on the IBM Spectrum
  Protect Plus appliance console to generate log bundle, it fails
  with 'Cannot allocate memory' error:
  
  [serveradmin@SPP-host scripts]#
  /opt/ECX/tools/logcollect/logcollect
  
  A log file for this run is created at:
     /opt/ECX/tools/logcollect/logs/logcollect_log_<date+time>.txt
  
  Enter username: admin
  Enter password:
  OpenJDK 64-Bit Server VM warning: INFO:
  os::commit_memory(0x00000004df680000, 1278214144, 0) failed;
  error='Cannot allocate memory' (errno=12)
  #
  # There is insufficient memory for the Java Runtime Environment
  to continue.
  # Native memory allocation (mmap) failed to map 1278214144
  bytes for committing reserved memory.
  # An error report file with more information is saved as:
  # /opt/ECX/virgo/repository/ecx-usr/hs_err_pidxxxxx.log
  
  The memory exhaustion happens when collecting the VM summary
  information during log collection. The hs_err_pidxxxxx.log
  displays following call stack:
  
  Stack:
  [0x00007fed66621000,0x00007fed66721000], sp=0x00007fed6671f060,
  free space=1016k
  Native frames: (J=compiled Java code,
  j=interpreted, Vv=VM code, C=native code)
  V
  [libjvm.so+0xadf8ed] VMError::report_and_die()+0x15d
  V
  [libjvm.so+0x4f4c6a] report_vm_out_of_memory(char const*, int,
  unsigned long, VMErrorType, char const*)+0xaa
  V
  [libjvm.so+0x8c32f8] os::pd_commit_memory(char*, unsigned long,
  unsigned long, bool)+0xd8
  V [libjvm.so+0x8ba5fe]
  os::commit_memory(char*, unsigned long, unsigned long,
  bool)+0x2e
  V [libjvm.so+0x936deb]
  PSVirtualSpace::expand_by(unsigned long)+0x5b
  V
  [libjvm.so+0x92760a] PSOldGen::expand_by(unsigned long) [clone
  .part.113]+0x2a
  V [libjvm.so+0x9277db]
  PSOldGen::expand(unsigned long) [clone .part.115]+0xdb
  V
  [libjvm.so+0x927a68] PSOldGen::allocate(unsigned long)+0xf8
  V
  [libjvm.so+0x8e7110]
  ParallelScavengeHeap::mem_allocate(unsigned long,
  bool*)+0x1d0
  V [libjvm.so+0xaa48d0]
  TypeArrayKlass::allocate_common(int, bool, Thread*)+0x240
  V
  [libjvm.so+0x95edd6] OptoRuntime::new_array_nozero_C(Klass*,
  int, JavaThread*)+0x26
  v ~RuntimeStub::_new_array_nozero_Java
  J
  469 C2 java.lang.String.<init>([CII)V (82 bytes) @
  0x00007fed5095baf8 [0x00007fed5095b900+0x1f8]
  J 95 C1
  java.lang.StringBuilder.toString()Ljava/lang/String; (17 bytes)
  @ 0x00007fed5088405c [0x00007fed50883f80+0xdc]
  j com.fasterxml.j
  ackson.core.util.TextBuffer.contentsAsString()Ljava/lang/String;
  +208
  j com.fasterxml.jackson.core.io.SegmentedStringWriter.getAn
  dClear()Ljava/lang/String;+4
  j com.fasterxml.jackson.databind.Ob
  jectWriter.writeValueAsString(Ljava/lang/Object;)Ljava/lang/Stri
  ng;+41
  j com.syncsort.dp.xsb.logcollect.LogCollector.downloadVmS
  ummary(Ljava/lang/String;)V+118
  j com.syncsort.dp.xsb.logcollect
  .LogCollector.updateListForItems()V+296
  j com.syncsort.dp.xsb.lo
  gcollect.LogCollector.processOptions()V+5
  j com.syncsort.dp.xsb.
  logcollect.LogCollector.startCollectingLogs(Ljava/io/OutputStrea
  m;)V+1
  j com.syncsort.dp.xsb.logcollect.LogCollector.main([Ljava
  /lang/String;)V+98
  v ~StubRoutines::call_stub
  V
  [libjvm.so+0x67dd1e] JavaCalls::call_helper(JavaValue*,
  methodHandle*, JavaCallArguments*, Thread*)+0xf5e
  V
  [libjvm.so+0x68e9fa] jni_invoke_static(JNIEnv_*, JavaValue*,
  _jobject*, JNICallType, _jmethodID*, JNI_ArgumentPusher*,
  Thread*) [clone .isra.205]+0x30a
  V [libjvm.so+0x6a2af6]
  jni_CallStaticVoidMethod+0x186
  C [libjli.so+0x39c9]
  JavaMain+0xa29
  C [libpthread.so.0+0x7e65]
  start_thread+0xc5
  
  Versions affected: 10.1.5.* & 10.1.6.*
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.5, 10.1.6 and 10.1.7.   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the fixing level when available. This problem is       *
  * currently projected to be fixed in IBM Spectrum Protect Plus *
  * level 10.1.7 ifx2 and 10.1.8. Note that this is subject to   *
  * change at the discretion of IBM.                             *
  ****************************************************************
  

Problem conclusion

• Memory fix made so user no longer hits "cannot allocate memory"
  error.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels