Description | After invocation of an FSE command, the following error is reported: | |
| 6001 Problems accessing CORBA Naming Service. | |
Explanation | omniNames (CORBA Naming Service daemon (service)) is not running in the FSE | |
| implementation. | |
Workaround | Proceed as follows: | |
| 1. On the consolidated FSE system or FSE server, verify the status of the CORBA Naming | |
| Service daemon (service). | |
| Linux specific | |
| Run the command omniNames | |
| Windows specific | |
| Use the Services tool to check the status of the omniORB CORBA Naming Service. | |
| 2. If omniNames is stopped, you need to start it, together with other FSE processes: | |
| a. | Stop the FSE processes with the fse |
| b. | Start omniNames and FSE processes using the fse |
Description | After invocation of an FSE command, the following error is reported: |
| 6008 Cannot connect to Management Interface - probably not running. |
| 'Requested name does not yet exist in the NameService. |
| Giving up. FSE/mgr/<fse_server@company@com>/mif' |
Explanation | Most probably the Management Interface (the process |
Workaround | Check if |
| you must restart FSE with the fse |
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 |
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. |
246 Troubleshooting