[omniORB] OmniNames fails to start

[Battista, Richard M]

Hello,

During the installation of RedHawk in section 2.6 at http://redhawksdr.github.io/Documentation/mainch2.html#x4-120002.6 I receive an error when executing "sudo /sbin/service omniNames start". The message shows

Starting omniNames [FAILED]

I am running CentOS ver 6. I have followed the instructions for installation as described in this section. This includes editing the omniORB.cfg. I checked for typos. The RedHawk IDE functions correctly except when trying to start the device manager. The following message appears in a pop up: "Doman Launcher" has encountered a problem. The file does not exist for the external tool named Doman Manager REDHAWK_DEV. I assume this has something to do with not being able to start omniNames. If I'm wrong disregard.

The computer is stand alone and not connected to a network. Centos was installed, then the rpms for redhawk. I checked and port 2609 is not being used. I manually checked that all the dependencies are correct as shown in appendix C.2 at: http://redhawksdr.github.io/Documentation/mainap3.html#x29-344000C.2

Any help would be appreciated.

Thank you, Rich


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20130917/69c6d2ac/attachment.html>

[Duncan Grisby]

Post by Battista, Richard M
During the installation of RedHawk in section 2.6 at
http://redhawksdr.github.io/Documentation/mainch2.html#x4-120002.6 I
receive an error when executing ?sudo /sbin/service omniNames start?.
The message shows
Starting omniNames [FAILED]

omniNames will have output an error somewhere. If you're using RPMs
built from the spec file in the omniORB distribution, there will
probably be a file /var/omniNames/error.log. If not, you'll need to read
the init script to see what it does with omniNames debug output.

[...]

Post by Battista, Richard M
The computer is stand alone and not connected to a network.

When you say it's not connected to a network, does it have any
networking enabled at all? If it doesn't at least have a TCP loopback
interface, omniORB can't work.

Post by Battista, Richard M
Centos was installed, then the rpms for redhawk. I checked and port
2609 is not being used.

The port for the CORBA naming service is 2809, not 2609. Maybe you have
something already listening on that?

Duncan.