[omniORB] omniNames won't start
Tom O'Reilly
oreilly at mbari.org
Tue May 29 13:26:17 BST 2007
Hi Carlos,
> I think your problem is that another application is listening in port
> 2089, can you check this with netstat, for example?
I have verified with 'netstat' that no other process is using port 2089.
Could my problem be connected with omniORB's new ipv6 support?
Thanks,
Tom
----- Original Message -----
From: "Carlos" <carlos at canama.net>
To: "Tom O'Reilly" <oreilly at mbari.org>
Cc: <omniorb-list at omniorb-support.com>
Sent: Tuesday, May 29, 2007 12:15 PM
Subject: Re: [omniORB] omniNames won't start
El mar, 29-05-2007 a las 10:19 -0700, Tom O'Reilly escribió:
> Hello,
>
> I've installed omniORB 4.1.0 on my Redhat machine. According to the
> README.unix file, the only steps needed to start the naming service
> are as follows:
>
> Set the environment variable OMNINAMES_LOGDIR to a directory
> where the naming service omniNames can store its data. For example:
> OMNINAMES_LOGDIR=/wib/wob; export OMNINAMES_LOGDIR
>
> Start omniNames.
> $ omniNames -start &
>
> I do this, and get the following error message:
>
> omniORB -start &
> omniORB: Error: Unable to create an endpoint of this description:
> giop:tcp::2809
>
> Failed to initialise the POAs. Is omniNames already running?
>
I think your problem is that another application is listening in port
2089, can you check this with netstat, for example?
Cheers.
Carlos.
>
More information about the omniORB-list
mailing list