User's Manual

192 Troubleshooting
Description Each time an FSE 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 FSE
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 FSE command-line interface cannot
resolve it.
Workaround See the FSE Installation Guide, section ”Preparing Windows operating systems”, subsection
”Verifying and modifying the primary DNS suffix of the system”.
Description Command fse --stop is not able to stop all FSE processes or abort all FSE jobs.
Explanation On heavily loaded systems, the fse --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 the FSE implementation on such systems:
1. Stop all non-FSE processes which are creating files on the HSM file system.
2. Unmount the HSM file systems.
3. Abort all FSE jobs using commands fsejob --list and fsejob --abort.
4. Stop all FSE jobs using fse --stop command.
Description In a private network environment, the FSE implementation does not start after the YaST2
configuration tool is run (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 Starting FSE services on Linux client causes kernel panic with the following message: "Unable
to handle kernel NULL pointer dereference at virtual address 00000018" (Linux
system-specific).
Explanation This message will be displayed in case that client has 3.1.89 (FSE 3.1 Patch 01) build installed,
and server has the latest (FSE 3.1 Patch 02) build installed.
Workaround Upgrade the client with the latest patch and then reboot it. During the reboot, ignore error
messages from fse-fsevtmgr (error: -19). After the reboot, FSE services can be started and the
HSMFS can be mounted without problems.