Startup and shut-down problems

Description

After running the ivd --stop command to shut down OpenArchive (OA), you may experience the following situation:
The ivd command does not finish (does not return to the command prompt) in a reasonable time.
Local HSM file systems are still mounted.
Local OA processes are still running.

Explanation

If a pre-stop script has been configured on this system, the above symptoms may indicate problems with commands in the script. Most probably one of the script commands has not finished.

Workaround

Identify the problematic command and reconfigure the script, as follows:
For each command that is specified in the pre-stop script (the pre_stop.sh file located in the local directory /opt/ivd/sbin), run the following command on the local system:
# ps -ef | grep CommandName
This will help you identify which command caused the shut-down problem.

Description

After invocation of the ivd --start command on a particular OA system host, some OA processes that should be started on the host (consolidated OA system, OA server or external OA client) are not running.

(SUSE Linux Enterprise Server system specific)

Explanation

If the required OA packages were installed on the host using a single rpm command, some of the packages may not have been installed correctly, due to unresolved dependencies. The reason for this is the rpm command included in the SUSE Linux distributions, which does not automatically sort the specified packages in order to resolve their dependencies.

Workaround

Check which packages have been successfully installed on the system:
1. At the command prompt, enter:
# ls -a /etc/opt/ivd
2. Inspect the command output for files that determine installed packages. On a consolidated OA system, check for the following files:
.agent.pkg
.cli-admin.pkg
.cli-user.pkg
.client.pkg
.common.pkg
.server.pkg

On an OA server, check for the following files:
.agent.pkg
.cli-admin.pkg
.common.pkg
.server.pkg
On an external OA client, check for the following files:
.cli-user.pkg
.client.pkg
.common.pkg

If any of the above files are missing, perform the following steps to reinstall the required
packages:

a. Determine which packages you tried to install, as follows:
# rpm -qa | grep "^ivd-" | grep -v ivd-gui.client.pkg
b. Reinstall all the packages listed in the command output. Use the sequence described in chapter ”Installing OA software” in the OA Installation Guide for Linux, and the following command to reinstall each package:
# rpm -U --replacepkgs --replacefiles PackageName

Description

Each time an OA command is invoked, the following error message is displayed:
ERROR 6008: Cannot connect to Management Interface - probably not running after system reboot. Requested name does not yet exist in the NameService. Giving up.

Explanation

The local services.cfg file contains the fully qualified domain name (FQDN) of the OA server host, where MIF is running. If the primary DNS suffix of this host is not set appropriately, the full computer name may contain only the host name. In this case, MIF registers itself in the CORBA Naming Service under a different name, and the OA command-line interface cannot resolve it.

Workaround

See the OA Installation Guide for Linux, chapter ”Preparing the operating system environment”, section ”Preparing the operating system”, subsection ”Verifying and modifying the primary DNS suffix of the system”.

Description

Command ivd --stop is not able to stop all OA processes or abort all OA jobs.

Explanation

On heavily loaded systems, the ivd --stop command is not able to abort all jobs within a short time, especially if at the same time, new jobs are created.

Workaround

To terminate OA processes on such systems:

1. Stop all non-OA processes which are creating files on the HSM file system.
2. Unmount the HSM file systems.
3. Abort all OA jobs using commands ivdjob --list and ivdjob --abort.
4. Stop all OA jobs using ivd --stop command.

Description

In a private network environment, the OA implementation does not start after the YaST2 configuration tool is run.

(SUSE Linux system specific)

Explanation

On a Linux system equipped with two network adapters, YaST2 modifies the /etc/hosts file and assigns the IP addresses (IP numbers) of both network adapters to the primary host name. omniORB cannot work with such a configuration.

Workaround

Manually edit the /etc/hosts file and revert back to the old host-name settings.

Description

If a consolidated OA system or OA server has a power failure, external OA clients are not automatically reconnected to the server after it is restarted.

Explanation n/a

Workaround

Stop all OA processes on the OA server and all external OA clients. Restart the services on the OA server first, then restart the processes on the external OA clients. Unexpected power failure of the OA server may result in a condition where you cannot stop the OA client processes with the ivd --stop command. In this case, use native operating system tools to terminate all OA processes. Use the kill command to terminate the OA processes.