This appendix provides a detailed explanation of the checks performed by the ruei-check.sh
script. It is strongly recommended that you use this script to verify successful installation, and to troubleshoot any installation issues.
The script's location is explained in Section 2.7.5, "Creating the Reporter Database Instance", and should be run as the root
user. When started, the script prompts you to specify which role or roles the system is required to perform. For example:
Please specify which role(s) this system will perform. Use commas to separate multiple roles. For example, 1,2,4 1 - Reporter 2 - Processing Engine 3 - Collector 4 - Database Enter role(s): 1,2,3,4
The permitted role combinations are shown in Table E-1.
Table E-1 Permitted System Role Combinations
Roles | Description |
---|---|
|
Reporter only. |
|
Processing Engine only. |
|
(Remote) Collector only. |
|
(Remote) database only. |
|
Reporter with Processing Engine. |
|
Reporter with Collector and Processing Engine. |
|
Reporter with Processing Engine and database. |
|
Reporter with Processing Engine, Collector, and database. |
The checks are performed in the order shown in Table E-2, and are divided into three types: pre-installation, system, and post-installation checks. Whether a specific check is performed depends on the selected role(s).
Table E-2 ruei-check.sh Checks
Role | |||||
---|---|---|---|---|---|
Check | 1 | 2 | 3 | 4 | Description |
System checks |
|||||
Architecture |
• |
• |
• |
• |
Must be x86_64. |
Operating system |
• |
• |
• |
• |
Must be Oracle/RedHat Linux 5.x or 6.x. |
Memory |
• |
• |
• |
• |
Must be at least 4 GB. Recommended 16 GB for Reporter installation. Recommended 8 GB for a Collector only or remote database installation. |
Swap space |
• |
• |
• |
• |
Must be at least 3/4 of the installed system memoryFoot 1 . |
Disk space for |
• |
• |
• |
The disk space for the specified |
|
Disk space for |
• |
• |
• |
The disk space for the specified |
|
Disk speed on |
• |
• |
• |
The disk speed of the specified |
|
SELinux |
• |
• |
• |
• |
SELinux must be disabled. |
Network interfaces |
• |
Must have at least one interface must be Up without an IP address. |
|||
Hostname |
• |
• |
• |
• |
The system's configured IP address and hostname must be specified in the |
DNS |
• |
• |
• |
• |
The configured DNS server must resolve the system's configured hostname to its IP address. |
HTTPD autostart |
• |
Must be configured to start automatically. |
|||
HTTPD up |
• |
Must be up. |
|||
Database autostart |
• |
Must be configured to start automatically. |
|||
SSHD autostart |
• |
• |
• |
• |
Must be configured to start automatically. |
SSHD up |
• |
• |
• |
• |
Must be up. |
SSHD |
• |
• |
• |
• |
Checks if the SSH is not firewalled. |
NTPD autostart |
• |
• |
• |
• |
Must be configured to start automatically. |
NTPD up |
• |
• |
• |
• |
Must be up. |
NTPD |
• |
• |
• |
• |
Must be synchronized with a time server. |
PHP CLI |
• |
PHP must be available on the command line. |
|||
PHP settings |
• |
Zend Optimizer must be available (Linux version 5.x). Zend Guard Loader must be available (Linux version 6.x). (These appear as individual checks, and are only performed if the above check is passed). |
|||
PHP timezone |
• |
PHP must return the same timezone as the Reporter operating system. See Section G.15, "ruei-check.sh Script Reports PHP Timezone Error" for additional information. |
|||
RSVG |
• |
The |
|||
Pre-install checks |
|||||
Disk space for database data directory |
• |
Must be 500 GB. (If on the same partition as |
|||
Disk containing database data directory |
• |
Should be local. (Remote file systems, such as NFS, are not supported). |
|||
Disk speed of database data directory |
• |
Must be at least 40 MB/s (120 MB/s is recommended). |
|||
|
• |
• |
• |
The specified |
|
|
• |
User |
|||
User |
• |
User |
|||
User |
• |
User |
|||
User |
• |
• |
• |
The specified |
|
User |
• |
• |
• |
• |
User |
User |
• |
User |
|||
User |
• |
• |
User |
||
User |
• |
User |
|||
User |
• |
• |
• |
User |
|
User |
• |
• |
• |
User |
|
User |
• |
• |
• |
• |
User |
|
• |
The |
|||
|
• |
• |
The specified |
||
|
• |
The |
|||
|
• |
The specified |
|||
|
• |
• |
• |
The specified |
|
|
• |
• |
• |
The specified |
|
|
• |
• |
• |
The specified |
|
Permissions and ownership of |
• |
• |
• |
The Apache user must be able to read from the specified |
|
|
• |
• |
• |
The |
|
User |
• |
• |
The |
||
|
• |
• |
The |
||
|
• |
• |
The value specified for |
||
Post-install checks |
|||||
Reporter RPM check |
• |
The |
|||
Processing Engine check |
The |
||||
Collector RPM check |
• |
The |
|||
Java shared objects |
• |
The Java path must have been correctly added to the |
|||
GUI reachable |
• |
The Reporter GUI must be reachable via the local hostname on the secure interface (note if a self-signed certificate is found, a warning is generated). |
|||
Reporter GUI can reach database |
• |
The Reporter GUI must be able to contact to the database. |
|||
Permissions and ownership of Oracle wallet |
• |
• |
The Oracle wallet must be readable by the Apache user. |
||
Permissions and ownership of Oracle wallet |
• |
The Oracle wallet must be readable by the |
|||
Core binaries in path |
• |
• |
The specified |
Footnote 1 If memory is added to meet the memory requirement, this check may start failing.
Re-running the ruei-check.sh Script
Be aware that the role selection you make when running the script is saved to file. Therefore, if you want to re-run the script and be able to specify a different role or roles for the system, you need to delete the file /tmp/ruei-system-type
using the following command:
rm /tmp/ruei-system-type