User's Manual

196 Troubleshooting
Description When inspecting the FSE error log of an improperly operating FSE implementation, the
following error entry is detected:
This machine (localhost.localdomain) has only localhost IP.
Misconfigured DNS on host: localhost.localdomain. Official name
(hostent::h_name) is NULL.
Misconfigured DNS on host: localhost.localdomain. Official name
(hostent::h_name) should contain FQDN.
(Linux-system specific)
Explanation This behavior is caused by improper network configuration, when the network is not configured
properly to resolve its host name to the fully-qualified domain name (FQDN) and IP.
Workaround Check if the network settings (DHCP settings, the /etc/hosts file configuration, DNS
resolution configuration, and so on) are correct, and modify them if necessary.
Description After running the fsefile command with any of the following options: --history, --recall,
--migrate, --trigger-migration, the command fails and reports:
6004 Caught Corba exception.
Explanation See Workaround.
Workaround First, try to identify the problem as follows:
1. Find out the status of the FSE partition with the command:
fsepartition --status PartitionName
2. Check if the fse-hsm process is running on the corresponding FSE client.
Linux specific
Use the command ps -ef | grep fse-hsm.
Windows specific
Use Windows Task Manager for this purpose.
If the partition status is set to any other value than mounted, and the fse-hsm process is
running on the client, the problem may be caused by an improper configuration of the
omniORB.cfg files. For information on which omniORB.cfg settings are correct and how to
configure omniORB.cfg appropriately, see ”Reconfiguring FSE interprocess communication”
on page 75.
Description In a distributed or mixed FSE implementation, after the FSE server or the integrated FSE system
is restarted, the fsepartition -l -D command reports FSE partitions on external FSE clients as not
mounted.
Explanation The FSE server or the integrated FSE system lost connection with all external FSE clients after it
was restarted.
Workaround On each external FSE client, restart the FSE processes using the fse --restart command.
This needs to be done with the above FSE implementations each time after the FSE server or the
integrated FSE system is restarted.