Smarts installation fails without an error message

Products

• VMware

Issue/Introduction

Symptoms:




Smarts installation fails without an error message
Smarts suite does not install

Environment

VMware Smart Assurance - SMARTS

Resolution

There are may be multiple reasons why a Smarts installation may fail without an error message being generated. To troubleshoot this issue, complete the following steps. If you cannot find the problem and solution on your own, contact EMC Support for further troubleshooting and quote this solution ID. Collect and provide the data collected at each step to EMC Support as noted.

1. Get all the available options and application arguments for a Smarts installer file by running the help command as in the following example:
   
   ./setup-ACM-2_2_0_0-solaris.bin -is:help
   
   The help command should output the following options and application arguments which are available for the Smarts installer program:
   
    -is:log <filename>    The is:log option with the <filename> argument will log debug messages to <filename> argument you provide.
    -is:javahome <dir>  The <dir> argument is the JRE home directory that points to the directory containing bin/java.
    -is:tempdir <dir>      The <dir> argument is the temporary directory to be used by the launcher.
    -cp:a <classpath>    The -cp:a option with the <classpath> argument appends the <classpath> to the launcher's classpath.
    -cp:p <classpath>    The -cp:p option with the <classpath> argument prepends the <classpath> to the launcher's classpath.
    -is:extract                   Extracts the contents of the archive.
    -is:nospacecheck      Turns off the launcher disk space checking.
    -is:version                   Returns launcher version and exits.
    -is:help                         Prints this help message and exits
   
    
2. Use the available options and application arguments to investigate the problem with the Smarts installation. The usage for the commands in the preceding step is as follows:
   
   setup-ACM-2_2_0_0-solaris.bin [OPTIONS] [APPLICATION_ARGUMENTS]
   
   
   The following example would output log debug messages to the file name you provide as the <filename> argument:
   
   setup-ACM-2_2_0_0-solaris.bin  -is:log <filename>
   
    
3. If you cannot determine the problem using the preceding command options and arguments, run the following trace-log command (this will output a large amount of data).
   
   $bash -x   setup-SAM-7_1_0_0-sol.bin 2> trace-log
   
    
4. Run the md5sum command on the installation pkg as in the following example:
   
   fusion:suite$ md5sum setup-ACM-2_2_0_0-solaris.bin
   12eea3aa45b6789c123fe4bac56f7cf0  setup-ACM-2_2_0_0-solaris.bin
   
   
5. Contact EMC Support for further troubleshooting. Provide the log generated by the trace-log command and the md5sum command output.