Skip to Content
avatar image
Former Member

installation errors on ase16 awx linux ami

Trying to install ASE 16 on Linux 64-bit on AWS Linux AMI (based on CentOS). I get these errors when running ./setup.bin:

Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...

Launching installer...

[Last 4000 events in the event buffer]
  <thread>                      <time>  <id>          <description>
 140249117972224                  0.00  0x00000004    ERROR occured (/bas/sapjvm/71_REL/src/6/hotspot/src/share/vm/runtime/thread.cpp:5318): VMCOs::init failed
 140249117972224                  0.00  0x00000003    ERROR occured (/bas/sapjvm/71_REL/src/6/hotspot/src/share/vm/sap/jvmEnv.cpp:132): VMCOs::init: Initialization of the control area failed
 140249117972224                  0.00  0x00000002    ERROR occured (/bas/sapjvm/71_REL/src/6/hotspot/src/share/vm/sap/controls.cpp:275): Controls::init: Could not create control area. Maybe old VMs are still running.
 140249117972224                  0.00  0x00000001    ERROR occured (/bas/sapjvm/71_REL/src/6/hotspot/src/share/vm/sap/os_unix.inline.hpp:494): os::create_control_area: Could not create control area file /tmp/sap_jvm_500_25601 (2: No such file or directory)
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit. 

Don't know how to proceed. Please help.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Feb 03, 2017 at 08:42 PM

    Just taking a shot in the dark at this point ...

    "Could not create control area file ... No such file or directory" could come about for a couple reasons (I can think of):

    1 - the linux login you're running the installer under does not have write permission to /tmp; using the same linux login, what happens when you try:

    touch /tmp/sap_jvm_500_25601

    2 - the filesystem that /tmp resides on filled up; by default the installer uses /tmp to hold intermediate scratch files and can easily require upwards of 1GB+ of space; it's not apparent from your post if the installer died right away or if it failed after running for a period of time; I'd suggest:

    - free up as much space in /tmp as you can (eg, 'rm' files/directories owned by your linux login)
    - while running the installer in one linux session/window ...
    - open a second linux session/window and repeatedly run: df -k /tmp
    - if the amount of available space in /tmp approaches 0, and the installer dies at about the same time, then you know you don't have enough room in /tmp

    If you find you're running out of space in /tmp, and you can't increase the amount of available free space under /tmp, you can try telling the installer to use an alternative directory/filesystem that does have enough space (eg, 2-4 GB just to be safe) (and make sure your linux login has write permissions in said directory!); to point the installer at an alternative scratch directory run the following in the same linux session where you plan on running the installer:

    IATEMPDIR=/alt/scratch/directory ; export IATEMPDIR
    Add comment
    10|10000 characters needed characters exceeded