000035614 - How to fix error "-bash: /usr/bin/Check_Instance_Running.sh: /bin/ksh: bad interpreter: No such file or directory" while installing RSA Identity Governance and Lifecycle

Document created by RSA Customer Support Employee on Nov 1, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000035614
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle 
RSA Version/Condition: 7.0.0+
 
IssueWhile performing a fresh installation of RSA Identity Governance and Lifecycle, the below error is seen:

[Fri Oct 6 18:15:53 CEST 2017] Start Wildfly to configure and load ear
-bash: /usr/bin/Check_Instance_Running.sh: /bin/ksh: bad interpreter: No such file or directory
Fresh install failed.. deleting /home/oracle/install, /home/oracle/Aveksa_System.cfg and /home/oracle/setDeployEnv.sh as part of cleanup.
Step failed! See /tmp/aveksa-install.log for more information.

 
CauseThe script “Check_Instance_Running.sh” interpreter is a ksh script and to interpret it you need ksh to be installed on OS. This error might be seen when:
1. You do not have ksh installed on the OS or the ksh shell (/bin/ksh or /usr/bin/ksh) is owned by a user other than root,or
2. It was removed from /bin or /usr/bin/ directory, or
3. The symbolic link was broken (ksh -> /bin/ksh93).
ResolutionInstall the KSH shell in the operating system to continue with the installation.
  1. Login as root user and run the below commands to check if the ksh is installed. 

    rpm -qa | grep ksh

  2. If there is no output for this command, it indicates there is no ksh in the operating system.
  3. Download the supported ksh file for the OS (RedHat or SuSE) online and place the file in /tmp directory.
  4. Run the below command  to install the ksh in the system. 

    rpm -ivh ksh-<version>.rpm

  5. Replace the <version> field with the version of the downloaded ksh script file.
  6. Once the ksh is installed, run the command in the first step to confirm ksh is present in the operating system.
  7. Uninstall RSA Identity Governance and Lifecycle and start a fresh installation with the steps mentioned in the Installation guide. 
 

Attachments

    Outcomes