User's Manual

hp StorageWorks File System Extender User Guide 195
Communication problems
Description CORBA cannot be initialized. After invocation of an FSE command, the following error is
reported:
FSE server specific
6000 Cannot initialize CORBA ORB. 'CORBA::COMM_FAILURE'
FSE client specific
Failed to initialize CORBA
Explanation Possible reason for this problem may be that omniNames is not running on the FSE server and,
consequentially, FSE server is not accessible to the FSE client.
Workaround Proceed as follows:
1. On the FSE server, verify the status of the CORBA Naming Service daemon (omniNames).
Invoke the omniNames --status command for this purpose, and restart it using the
omniNames --restart command, if needed.
2. On the FSE client, verify the settings specified in the omniORB.cfg file.The location of the
file is platform-dependent.
Linux specific
On Linux platform, omniORB.cfg is located in the directory /etc/opt/fse.
Windows specific
On Windows platform, omniORB.cfg is located in the directory %InstallPath%\etc.
The value of %InstallPath% depends on the choice made in the FSE installation process.
It defaults to C:\Program Files\Hewlett-Packard\FSE.
3. Check the network connection between the FSE client and the FSE server.
Description After invocation of an FSE command, the following error is reported:
6001 Problems accessing CORBA Naming Service.
Explanation omniNames (CORBA Naming Service daemon) is not running on FSE.
Workaround Check if omniNames is running by inspecting the output of the omniNames --status
command. If omniNames is stopped, proceed as follows:
1. Stop the FSE daemons/services with the fse --stop command.
2. Start the omniNames naming service and FSE daemons/services using the fse --start
command.
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 fse-mif) is not running.
Workaround Check if fse-mif is running using the fse --status command. If the process is stopped,
you must restart FSE with the fse --restart command.