Troubleshooting Linux Installations

The Jive installation uses Linux RPM, a widely tested and used application that is very unlikely to fail. However, if you run into trouble during an installation, you can delete and start over as described here.

Note: You'll find the installation log files on the target computer at /usr/local/jive/var/logs.

Unsatisfied Dependencies

The Jive application RPM depends on the presence of several low-level system packages that are common to nearly all configurations of Jive’s supported Linux distributions. Also, the Jive application RPM depends on three high-level packages. If any of these packages (system or high-level) is not present, the RPM subsystem will warn you, then refuse to install. When you see these warnings, simply install the missing packages using RPM, then install Jive as described in the instructions.

Unsatisfied dependencies appear as an error when attempting to install the Jive application:

[root@targethost ~]# ls -l
total 202068
-rw-r--r-- 1 root root 206701420 Jan 20 16:03 jive_sbs-5.0.0-78310.i386.rpm
-rwxr-xr-x 1 root root      1347 Oct  7 16:14 updateDNS.sh
[root@targethost ~]# rpm -ivh jive_sbs-5.0.0-78310.i386.rpm 
error: Failed dependencies:
     bash >= 3.2 is needed by jive_sbs-5.0.0-78310.i386
     sysstat >= 7 is needed by jive_sbs-5.0.0-78310.i386

Depending on the host configuration, it may be possible to install the dependencies directly using system tools. For example, in RedHat Enterprise Linux, the “yum” command can install dependencies via network repositories. The following demonstrates how to install the dependencies shown in the error above.

[root@targethost ~]# yum install bash-3.2 sysstat
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
extras                    100% |=========================| 1.1 kB    00:00 
updates                                                          951 B 00:00 
base                      100% |=========================| 1.1 kB    00:00 
addons                    100% |=========================|  951 B    00:00 
Reading repository metadata in from local files
primary.xml.gz            100% |=========================|  90 kB    00:00 
################################################## 295/295
primary.xml.gz                                                  369 kB 00:03 
################################################## 796/796
primary.xml.gz            100% |=========================| 853 kB    00:01 
################################################## 2458/2458
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for sysstat to pack into transaction set.
sysstat-7.0.2-1.el5.i386. 100% |=========================|  15 kB    00:00 
---> Package sysstat.i386 0:7.0.2-1.el5 set to be updated
---> Downloading header for bash to pack into transaction set.
bash-3.2-21.el5.i386.rpm  100% |=========================|  55 kB    00:00
---> Package bash.i386 0:3.2-21.el5 set to be updated
--> Running transaction check
Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Installing:
 sysstat                 i386       7.0.2-1.el5      base              168 k
Updating:
 bash                    i386       3.2-21.el5       base              1.9 M
Transaction Summary
=============================================================================
Install      1 Package(s) 
Update       1 Package(s) 
Remove       0 Package(s)
Total download size: 2.0 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): sysstat-7.0.2-1.el 100% |=========================| 168 kB    00:00 
(2/2): bash-3.2-21.el5.i3 100% |=========================| 1.9 MB    00:02 
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Updating  : bash                         ######################### [1/3] 
  Installing: sysstat                      ######################### [2/3] 
  Cleanup   : bash                         ######################### [3/3]
Installed: sysstat.i386 0:7.0.2-1.el5
Updated: bash.i386 0:3.2-21.el5
Complete!

After dependencies have been resolved, the package should install normally.

Insufficient System Memory

The Jive platform requires a minimum of 3GB of RAM to operate effectively for an enterprise environment. If sufficient memory is not available on the target installation system, the installer will provide a warning at installation time similar to the example below.

[root@targethost ~]# rpm -ivh jive_sbs-5.0.0-78310.i386.rpm
Preparing...                ########################################### [100%]
   1:jive_sbs               ########################################### [100%]
Writing installation version.
Wrote installation version.
Executing Jive post-install configuration.
Creating jive group jive.
Creating jive system user jive.
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
Marking all upgrades as complete.
WARNING: this host does not have sufficient RAM to run a production Jive system. 
A minimum of 3GB is required to host the application and HTTPD servers. 4GB is required to 
run a locally hosted database.
Starting Jive System Daemon.
Performing Jive system configurations.
Disabling CPU frequency stepping.
. . .
Jive post-install configuration complete.

In the above example, note the message “WARNING: this host does not have sufficient RAM to run a production system. A minimum of 3GB is required to host the application and HTTPD servers. 4GB is required to run a locally hosted database.”

Despite this warning, the package does install correctly; however, further errors are noted on the output line: "Failed to start application sbs. See log file at '/usr/local/jive/var/logs/sbs.out'." The contents of this log file indicate:

[root@targethost ~]# cat /usr/local/jive/var/logs/sbs.out
SCRIPT_DIR=/usr/local/jive/applications/sbs/bin
JIVE_BASE=/usr/local/jive/applications/sbs
Creating temp directory at /usr/local/jive/var/work/sbs.
Starting application sbs
Error occurred during initialization of VM
Could not reserve enough space for object heap

Starting Over

In the unlikely event that something goes wrong during installation and you want to start over, you can uninstall. When uninstalling, you don't specify the RPM filename, as you did when installing. Instead, provide the logical name by which the RPM now knows the application: jive_sbs. Here's an example using rpm -e for uninstalling:

rpm -e jive_sbs

If you want to be sure you've removed all remnants of the installation, delete the destination directory created by the RPM with:

rm -rf /usr/local/jive