000033901 - RSA Identity Governance and Lifecycle patch stalls at "Checking minimum disk sizes" step and fails to complete.

Document created by RSA Customer Support Employee on Sep 19, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000033901
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle, Identity Management and Governance
RSA Version/Condition: 7.0
IssueRSA Identity Governance and Lifecycle patch does not complete.  The last item displayed in the console is the step "Checking minimum disk sizes"
This is the log file content, log file location is /home/oracle/Aveksa_7.0.0_P02/logs, 
Begin ACM patch 7.0.0 P02 on cskpcloudxn0823
at Fri Aug 26 11:48:16 PDT 2016
Detailed output from this installation can be found in:
You can view the detailed installation log information while the install
is running by entering the following command in another console:
tail -f /home/oracle/Aveksa_7.0.0_P02/logs/7.0.0_P02_2016-08-26-1148.log

Checking environment...
-- Verifying existance of /home/oracle/Aveksa_System.cfg
-- Checking for need to update CustomizeACM.groovy for deployment fixes
--- No updates needed for file CustomizeACM.groovy
-- Expanding currently deployed ear to filesystem for further checks
customization dir being cleaned: /tmp/customizeACM
unzipping ear.../home/oracle/archive/aveksa_7.0.0_93958-2016-Aug-11-13.55.ear
    [unzip] Expanding: /home/oracle/archive/aveksa_7.0.0_93958-2016-Aug-11-13.55.ear into /tmp/customizeACM
Ready for customization. Please go to /tmp/customizeACM to continue modifications.
-- Checking Version Information
--- Proceeding: No patch currently installed.
-- Checking minimum disk sizes

The patch installation log file located at /home/oracle/Aveksa_7.0.0_{patch number}/logs (example /home/oracle/Aveksa_7.0.0_P02/logs) shows the same information.
CauseThis issue occurs at a step in the patch.sh shell script where it attempts to calculate free disks space if the unix user admin does not exist on the system.  The user admin is created during a typical installation but may be removed after the installation by customers who are attempting to increase the security of the system by reducing the number of unnecessary accounts.
WorkaroundRSA recommends temporarily creating an account called admin in order to allow the script to complete.  There are no specific requirements for this account except that it has a home directory defined.  The following unix command will create an account.
>useradd -m admin