Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2030692.1
Update Date:2017-05-18
Keywords:

Solution Type  Problem Resolution Sure

Solution  2030692.1 :   STA 2.1 - Install on Redhat Linux Fails on SELINUX disable check  


Related Items
  • Sun StorageTek SL3000 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
  •  




In this Document
Symptoms
Cause
Solution


Created from <SR 3-11026528281>

Applies to:

Sun StorageTek SL3000 Modular Library System - Version All Versions and later
Information in this document applies to any platform.

Symptoms

Working on a new install of STA 2.1 on a Redhat 6.6 Server.  The installer script is failing during the SELINUX disabled prerequisite check.

See the following in the STA install log (/Oracle/StorageTek_Tape_Analytics/inventory/logs/install<date>PM.log)

 

Checking Operating System has SELINUX disabled
Expected result: SELINUX is disabled
Actual result: SELINUX is not disabled
Check complete.  The overall result of this check is: Failed<<<<



However, SELINUX has been disabled as per the documentation:

[root@xxx tmp]# cat /etc/sysconfig/selinux
SELINUX=disabled

  

They have rebooted the Redhat box in order to make the above changes take effect.

Running the "sestatus" command returns with "SELinux status:                 disabled".

Cause

 The sestatus command is located at /usr/sbin/, which was not in the path for the user I was doing the install with. 

Solution

**

The exact command issued from the prereq checks is:

((sestatus && echo --EOF--) || echo --EOF--)


The typical response that we get back will be something like"

SELinux status:          disabled

--EOF--


we use the string "--EOF--" to make it easier to manipulate the return value.

We then check the returned value to check that it contains the keyword "disabled" . This is done through java.

Have the site run the installer with the parameters  sta_install.....   "-debug -logLevel finest" and get the log files back.  It may be able to give us an insight to what is wrong. At this stage of the installer, the log files will typically be located in the /tmp/oraInst<timestamp> directory. You should be able to tell when the installer runs, which directory in /tmp its running from.

**


As per the above, after running the install script in -debug mode:

Running the installer in debug mode it looks like the installer is unable to find the "sestatus" command.

Run command : sestatus
Result : /bin/bash: line 16: sestatus: command not found


The sestatus command is located at /usr/sbin/, which was not in the path for the user doing the install.  

Added /usr/sbin to the path for the user and the check passed.  The STA install completed successfully.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback