Layer7 Access Management

Expand all | Collapse all

SDK Installation Error

Jump to Best Answer
  • 1.  SDK Installation Error

    Posted 06-06-2017 06:31 PM

    I'm trying to install SiteMinder WAM SDK 12.62 on a RHL 7 server. i have installed Jdk 1.8.131 with JCE files. But i keep getting the following error :

     

    (Installation running as root )


    Launching installer...

    ========= VM Command Line ============================================
    options:
    CLASSPATH:/tmp/install.dir.24602/InstallerData:/tmp/install.dir.24602/InstallerData/installer.zip:

    ========= Forking JAVA =============================================
    JRE libraries are missing or not compatible....
    Exiting....
    ========= JAVA Finished ==============================================

     

     

    When i checked the installation instructions, it suggest to install ETPKI directories but i do not see any setup command utilities with the zip file downloaded fro the site ( SDK zip file for Linux).

     

    Any help is apprecaited.



  • 2.  Re: SDK Installation Error

    Posted 06-07-2017 03:11 AM

    12.6 needs 64 bit JDK. Did you install 64 bit or 32 bit ?



  • 3.  Re: SDK Installation Error

    Posted 06-07-2017 03:14 AM

    yes i did install a 64 bit Java - 

     

    SDK binary file: ca-sdk-12.6-sp02-linux-x86-64.bin

     

    [root@pingfed-sandbox ~]# java -version
    java version "1.8.0_131"
    Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
    Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
    [root@pingfed-sandbox ~]# which java
    /opt/jdk1.8.0_131/jre/bin/java



  • 4.  Re: SDK Installation Error

    Posted 06-07-2017 03:18 AM

    Hmm, can you create installation debug file please ..

     

    1. Set LAX_DEBUG=file 

    2. Run your installer. 

    3. Once the install is complete a file labeled jx.log will be generated in the same directory as your installer. This file will contain the entire debug output generated by the install.

     

    Reference : IBM How to debug InstallAnywhere when installing Connect Java based products - United States 

    Then , please upload the jx.log for review.



  • 5.  Re: SDK Installation Error

    Posted 06-07-2017 03:29 AM

    root@pingfed-sandbox pfuser]# export LAX_DEBUG=true
    [root@pingfed-sandbox pfuser]# ./ca-sdk-12.6-sp02-linux-x86-64.bin -i console
    Preparing to install...
    Checking for POSIX df.
    Found POSIX df.
    Checking tail options...
    Using tail -n 1.
    True location of the self extractor: /home/pfadmin/pfuser/ca-sdk-12.6-sp02-linux-x86-64.bin
    Creating installer data directory: /tmp/install.dir.26019
    Creating installer data directory: /tmp/install.dir.26019/InstallerData
    Gathering free-space information...
    Space needed to complete the self-extraction: 702000 blocks
    Available space: 5020184 blocks
    Available blocks: 5020184 Needed blocks: 702000 (block = 512 bytes)
    Computed number of blocks to extract: 2191
    Extracting the JRE from the installer archive...
    Extracting JRE from ./ca-sdk-12.6-sp02-linux-x86-64.bin to /tmp/install.dir.26019/Linux/resource/jre_padded ...
    Extracting done, exit code = 0
    Extracting JRE from /tmp/install.dir.26019/Linux/resource/jre_padded to /tmp/install.dir.26019/Linux/resource/vm.tar.Z ...
    Extracting done, exit code = 0
    Unpacking the JRE...
    Unpacking the JRE...
    gzip is /usr/bin/gzip
    GZIP done.
    TAR done.
    Extracting the installation resources from the installer archive...
    Extracting install.zip from ./ca-sdk-12.6-sp02-linux-x86-64.bin to /tmp/install.dir.26019/InstallerData/installer.padded ...
    Extracting to padded done, exit code = 0
    Extracting from padded to zip done, exit code = 0
    Creating disk1 data directory: /tmp/install.dir.26019/InstallerData/Disk1
    Creating instdata data directory: /tmp/install.dir.26019/InstallerData/Disk1/InstData
    Extracting resources from ./ca-sdk-12.6-sp02-linux-x86-64.bin to /tmp/install.dir.26019/InstallerData/Disk1/InstData/Resource1.zip ...
    Extracting done, exit code = 0
    Configuring the installer for this system's environment...

    ========= Analyzing UNIX Environment =================================
    Setting UNIX (linux) flavor specifics.
    Importing UNIX environment into LAX properties.
    Checking for POSIX awk.

    ========= Analyzing LAX ==============================================
    LAX found............................ OK.
    LAX properties read.................. OK.

    ========= Finding VM =================================================
    Valid VM types.......................... 1.5+
    Absolute LAX_VM path.................... /tmp/install.dir.26019/Linux/resource/jre/bin/java
    Expanded Valid VM types................. 1.5+
    Found jvmspecs.properties

    ========= Virtual Machine Options ====================================
    LAX properties incorporated............. OK.
    classpath............................... "/tmp/install.dir.26019/InstallerData:/tmp/install.dir.26019/InstallerData/installer.zip"
    main class.............................. "com.zerog.ia.installer.Main"
    .lax file path.......................... "/tmp/install.dir.26019/temp.lax"
    user directory.......................... "/tmp/install.dir.26019"
    stdout to............................... "console"
    sterr to................................ "console"
    install directory....................... ""
    JIT..................................... none
    option (verify)......................... off
    option (verbosity)...................... none
    option (garbage collection extent)...... none
    option (garbage collection thread)...... none
    option (native stack max size).......... none
    option (java stack max size)............ none
    option (java heap max size)............. 50331648
    option (java heap initial size)......... 16777216
    option (lax.nl.java.option.additional).. none

    ========= Display settings ===========================================
    X display............................... not set
    UI mode................................. console

    Launching installer...

    ========= VM Command Line ============================================
    options:
    CLASSPATH:/tmp/install.dir.26019/InstallerData:/tmp/install.dir.26019/InstallerData/installer.zip:

    ========= Forking JAVA =============================================
    JRE libraries are missing or not compatible....
    Exiting....
    ========= JAVA Finished ==============================================



  • 6.  Re: SDK Installation Error
    Best Answer

    Posted 06-07-2017 03:34 AM

    Can you try running following command :

     

    a. sudo su

    b. cd /

    c. mkdir tmp2

    d. IATEMPDIR=/tmp2

    e. export IATEMPDIR



  • 7.  Re: SDK Installation Error

    Posted 06-07-2017 03:40 AM

    Done. 

     

    And then do you want me to run the installer?

     

    Thanks



  • 8.  Re: SDK Installation Error

    Posted 06-07-2017 03:40 AM

    Yes please



  • 9.  Re: SDK Installation Error

    Posted 06-07-2017 03:58 AM

    That helped. It looks like the /tmp directory was not having enough space for the installer to extract the files. Now was there any thing in the information provided above lead you to this thought? 


    Thanks



  • 10.  Re: SDK Installation Error

    Posted 06-07-2017 04:05 AM

    Nice. Nothing much except the fact that you were using "/tmp" for your installation temp directory.

    This is one of the very common issue while using this installation software (installanywhere)



  • 11.  Re: SDK Installation Error

    Posted 06-07-2017 04:07 AM

    Thanks for your quick reply on this. 



  • 12.  Re: SDK Installation Error

    Posted 06-07-2017 05:12 AM

    Hello Ujwol,

                             Is there any environmental variables that needs to be set for the SDK? I don't see any environmental script file. I'm trying to run the smreghost command but keep getting error as following:

     

    smreghost: error while loading shared libraries: libsmcommonutil.so: cannot open shared object file: No such file or directory