IBM Support

RHEL 5.0 Error message "Failed to find VM - aborting" when invoking TDI Server, CE or other TDI commands

Question & Answer


When running TDI on RHEL 5.0 machine, a user may see the error "Failed to find VM - aborting" when trying to invoke the TDI server, CE or other TDI commands.


RHEL 5.0 has a new security feature named 'Security Enhanced Linux', or SELinux for short. A weaker version of SELinux was included in RHEL 4.0, and was disabled by default. RHEL 5.0 defaults SELinux to enabled. SELinux helps to keep the host secure from certain types of malicious attacks. However, the default settings have been known in many cases to prevent Java 1.5 from running properly. TDI 6.1.1 ships with IBM Java 1.5-SR5. When these JRE 1.5 issues occur, the /var/log/messages file may contain cryptic error messages describing what is not allowed.


To fix this issue, you can choose one of the following options:

  • Change the mode of SELinux to 'Permissive' by entering 'setenforce 0' on the command line. SELinux will be fully enabled again the next time the system is rebooted or if "setenforce 1" is entered on the command line.
  • Configure SELinux so that it knows that the IBM JRE 1.5 shared libraries shipped with TDI are acceptable to run. This can be accomplished by running the semanage and chcon commands properly on all shared libraries shipped with the JRE. Below is a piece of an example shell script that shows how to do this:

   for I in `ls <tdi_install_dir>/jvm/jre/bin/lib*.so`
      semanage fcontext -a -t textrel_shlib_t ${I}
      chcon -f -t textrel_shlib_t ${I};
   semanage fcontext -a -t textrel_shlib_t \
   chcon -f -t textrel_shlib_t \

NOTE: The actual install path would be substitued for <tdi_install_dir> (for example /opt/IBM/TDI/V6.1.1)

[{"Product":{"code":"SSCQGF","label":"Tivoli Directory Integrator"},"Business Unit":{"code":"BU008","label":"Security"},"Component":"General","Platform":[{"code":"PF016","label":"Linux"}],"Version":"6.1.1","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018