Discussion:
[omniORB] omniNames won't start
Tom O'Reilly
2007-05-29 23:19:51 UTC
Permalink
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?

The directory pointed to by $OMNINAMES_LOGDIR is empty, so apparently the naming service never started.

I've been reading documentation for a few hours, but cannot find any more details on how to start the naming service. Does anyone know where I can find such documentation? Are there other steps I must take that are not documented in README.unix?

I then set tracelevel=20, but I don't know where to look for clues - here is the output of "omniNames -start":

omniORB: Distribution date: Tue Nov 28 13:27:23 GMT 2006 dgrisby
omniORB: My addresses are:
omniORB: 127.0.0.1
omniORB: 134.89.28.204
omniORB: Native char code sets: ISO-8859-1 UTF-8.
omniORB: Transmission char code sets: ISO-8859-1(1.2) ISO-8859-1(1.1) ISO-8859
(1.0) UTF-8(1.2) UTF-8(1.1).
omniORB: Native wide char code sets: UTF-16.
omniORB: Transmission wide char code sets: UTF-16(1.2).
omniORB: Information: the omniDynamic library is not linked.
omniORB: Current configuration is as follows:
omniORB: DefaultInitRef (file) =
omniORB: DefaultInitRef (args) =
omniORB: InitRef = NameService=corbaname::morgana.shore.mbari.org
omniORB: abortOnInternalError = 0
omniORB: abortOnNativeException = 0
omniORB: acceptBiDirectionalGIOP = 0
omniORB: acceptMisalignedTcIndirections = 0
omniORB: bootstrapAgentHostname =
omniORB: bootstrapAgentPort = 900
omniORB: clientCallTimeOutPeriod = 0
omniORB: clientConnectTimeOutPeriod = 0
omniORB: clientTransportRule = * unix,ssl,tcp
omniORB: configFile = /home/oreilly/omniORB/omniORB.cfg
omniORB: connectionWatchImmediate = 0
omniORB: connectionWatchPeriod = 50000
omniORB: copyValuesInLocalCalls = 1
omniORB: diiThrowsSysExceptions = 0
omniORB: dumpConfiguration = 0
omniORB: endPoint = giop:tcp:morgana.shore.mbari.org:
omniORB: endPoint = giop:tcp::2809
omniORB: endPointPublish = addr
omniORB: giopMaxMsgSize = 2097152
omniORB: giopTargetAddressMode = KeyAddr
omniORB: id = omniORB4
omniORB: idleThreadTimeout = 10
omniORB: inConScanPeriod = 180
omniORB: lcdMode = 0
omniORB: maxGIOPConnectionPerServer = 5
omniORB: maxGIOPVersion = 1.2
omniORB: maxInterleavedCallsPerConnection = 5
omniORB: maxServerThreadPerConnection = 100
omniORB: maxServerThreadPoolSize = 100
omniORB: maxSocketRecv = 2147483647
omniORB: maxGIOPVersion = 1.2
omniORB: maxInterleavedCallsPerConnection = 5
omniORB: maxServerThreadPerConnection = 100
omniORB: maxServerThreadPoolSize = 100
omniORB: maxSocketRecv = 2147483647
omniORB: maxSocketSend = 2147483647
omniORB: nativeCharCodeSet = ISO-8859-1
omniORB: nativeWCharCodeSet = UTF-16
omniORB: objectTableSize = 0
omniORB: offerBiDirectionalGIOP = 0
omniORB: oneCallPerConnection = 1
omniORB: outConScanPeriod = 120
omniORB: poaHoldRequestTimeout = 0
omniORB: poaUniquePersistentSystemIds = 1
omniORB: principal = [Null]
omniORB: scanGranularity = 5
omniORB: serverCallTimeOutPeriod = 0
omniORB: serverTransportRule = * unix,ssl,tcp
omniORB: strictIIOP = 1
omniORB: supportBootstrapAgent = 0
omniORB: supportCurrent = 1
omniORB: supportPerThreadTimeOut = 0
omniORB: tcAliasExpand = 0
omniORB: threadPerConnectionLowerLimit = 9000
omniORB: threadPerConnectionPolicy = 1
omniORB: threadPerConnectionUpperLimit = 10000
omniORB: threadPoolWatchConnection = 1
omniORB: traceExceptions = 0
omniORB: traceFile = [stderr]
omniORB: traceInvocationReturns = 0
omniORB: traceInvocations = 0
omniORB: traceLevel = 20
omniORB: traceThreadId = 0
omniORB: traceTime = 0
omniORB: unixTransportDirectory = /tmp/omni-%u
omniORB: unixTransportPermission = 777
omniORB: useTypeCodeIndirections = 1
omniORB: verifyObjectExistsAndType = 1
omniORB: Initialising incoming endpoints.
omniORB: Instantiate endpoint 'giop:tcp:morgana.shore.mbari.org:'
omniORB: Instantiate endpoint 'giop:tcp::2809'
omniORB: Error: Unable to create an endpoint of this description: giop:tcp::2809
Failed to initialise the POAs. Is omniNames already running?
omniORB: ORB not destroyed; no final clean-up.


Many thanks,
Tom


--------------------------------------------------
Thomas C. O'Reilly
Monterey Bay Aquarium Research Institute
7700 Sandholdt Road
Moss Landing, California 95039-9644
831-775-1766 (voice)
831-775-1620 (FAX)
***@mbari.org (email)
http://www.mbari.org (World-wide Web)

"The machine does not isolate man from the great mysteries
of nature, but plunges him more deeply into them."

- ANTOINE DE SAINT-EXUPERY
"Wind, Sand, and Stars" (1939)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20070529/51e8d2fd/attachment.htm
Carlos
2007-05-30 01:14:08 UTC
Permalink
Post by Tom O'Reilly
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
Set the environment variable OMNINAMES_LOGDIR to a directory
OMNINAMES_LOGDIR=/wib/wob; export OMNINAMES_LOGDIR
Start omniNames.
$ omniNames -start &
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.
Tom O'Reilly
2007-05-30 01:26:40 UTC
Permalink
Hi Carlos,
Post by 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" <***@canama.net>
To: "Tom O'Reilly" <***@mbari.org>
Cc: <omniorb-***@omniorb-support.com>
Sent: Tuesday, May 29, 2007 12:15 PM
Subject: Re: [omniORB] omniNames won't start
Post by Carlos
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
Set the environment variable OMNINAMES_LOGDIR to a directory
OMNINAMES_LOGDIR=/wib/wob; export OMNINAMES_LOGDIR
Start omniNames.
$ omniNames -start &
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.
Tom O'Reilly
2007-05-30 01:43:40 UTC
Permalink
It seems that the error described below is connected to omniORB ipv6 support. I rebuilt and installed omniORB 4.1.0, after running 'configure' with the '--disable-ipv6' argument. Now 'omniNames -start' runs without apparent error.

Is there some other way to solve this without disabling ipv6?

Thanks,
Tom

----- Original Message -----
From: Tom O'Reilly
To: omniorb-***@omniorb-support.com
Sent: Tuesday, May 29, 2007 10:19 AM
Subject: [omniORB] omniNames won't start


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?

The directory pointed to by $OMNINAMES_LOGDIR is empty, so apparently the naming service never started.

I've been reading documentation for a few hours, but cannot find any more details on how to start the naming service. Does anyone know where I can find such documentation? Are there other steps I must take that are not documented in README.unix?

I then set tracelevel=20, but I don't know where to look for clues - here is the output of "omniNames -start":

omniORB: Distribution date: Tue Nov 28 13:27:23 GMT 2006 dgrisby
omniORB: My addresses are:
omniORB: 127.0.0.1
omniORB: 134.89.28.204
omniORB: Native char code sets: ISO-8859-1 UTF-8.
omniORB: Transmission char code sets: ISO-8859-1(1.2) ISO-8859-1(1.1) ISO-8859
(1.0) UTF-8(1.2) UTF-8(1.1).
omniORB: Native wide char code sets: UTF-16.
omniORB: Transmission wide char code sets: UTF-16(1.2).
omniORB: Information: the omniDynamic library is not linked.
omniORB: Current configuration is as follows:
omniORB: DefaultInitRef (file) =
omniORB: DefaultInitRef (args) =
omniORB: InitRef = NameService=corbaname::morgana.shore.mbari.org
omniORB: abortOnInternalError = 0
omniORB: abortOnNativeException = 0
omniORB: acceptBiDirectionalGIOP = 0
omniORB: acceptMisalignedTcIndirections = 0
omniORB: bootstrapAgentHostname =
omniORB: bootstrapAgentPort = 900
omniORB: clientCallTimeOutPeriod = 0
omniORB: clientConnectTimeOutPeriod = 0
omniORB: clientTransportRule = * unix,ssl,tcp
omniORB: configFile = /home/oreilly/omniORB/omniORB.cfg
omniORB: connectionWatchImmediate = 0
omniORB: connectionWatchPeriod = 50000
omniORB: copyValuesInLocalCalls = 1
omniORB: diiThrowsSysExceptions = 0
omniORB: dumpConfiguration = 0
omniORB: endPoint = giop:tcp:morgana.shore.mbari.org:
omniORB: endPoint = giop:tcp::2809
omniORB: endPointPublish = addr
omniORB: giopMaxMsgSize = 2097152
omniORB: giopTargetAddressMode = KeyAddr
omniORB: id = omniORB4
omniORB: idleThreadTimeout = 10
omniORB: inConScanPeriod = 180
omniORB: lcdMode = 0
omniORB: maxGIOPConnectionPerServer = 5
omniORB: maxGIOPVersion = 1.2
omniORB: maxInterleavedCallsPerConnection = 5
omniORB: maxServerThreadPerConnection = 100
omniORB: maxServerThreadPoolSize = 100
omniORB: maxSocketRecv = 2147483647
omniORB: maxGIOPVersion = 1.2
omniORB: maxInterleavedCallsPerConnection = 5
omniORB: maxServerThreadPerConnection = 100
omniORB: maxServerThreadPoolSize = 100
omniORB: maxSocketRecv = 2147483647
omniORB: maxSocketSend = 2147483647
omniORB: nativeCharCodeSet = ISO-8859-1
omniORB: nativeWCharCodeSet = UTF-16
omniORB: objectTableSize = 0
omniORB: offerBiDirectionalGIOP = 0
omniORB: oneCallPerConnection = 1
omniORB: outConScanPeriod = 120
omniORB: poaHoldRequestTimeout = 0
omniORB: poaUniquePersistentSystemIds = 1
omniORB: principal = [Null]
omniORB: scanGranularity = 5
omniORB: serverCallTimeOutPeriod = 0
omniORB: serverTransportRule = * unix,ssl,tcp
omniORB: strictIIOP = 1
omniORB: supportBootstrapAgent = 0
omniORB: supportCurrent = 1
omniORB: supportPerThreadTimeOut = 0
omniORB: tcAliasExpand = 0
omniORB: threadPerConnectionLowerLimit = 9000
omniORB: threadPerConnectionPolicy = 1
omniORB: threadPerConnectionUpperLimit = 10000
omniORB: threadPoolWatchConnection = 1
omniORB: traceExceptions = 0
omniORB: traceFile = [stderr]
omniORB: traceInvocationReturns = 0
omniORB: traceInvocations = 0
omniORB: traceLevel = 20
omniORB: traceThreadId = 0
omniORB: traceTime = 0
omniORB: unixTransportDirectory = /tmp/omni-%u
omniORB: unixTransportPermission = 777
omniORB: useTypeCodeIndirections = 1
omniORB: verifyObjectExistsAndType = 1
omniORB: Initialising incoming endpoints.
omniORB: Instantiate endpoint 'giop:tcp:morgana.shore.mbari.org:'
omniORB: Instantiate endpoint 'giop:tcp::2809'
omniORB: Error: Unable to create an endpoint of this description: giop:tcp::2809
Failed to initialise the POAs. Is omniNames already running?
omniORB: ORB not destroyed; no final clean-up.


Many thanks,
Tom


--------------------------------------------------
Thomas C. O'Reilly
Monterey Bay Aquarium Research Institute
7700 Sandholdt Road
Moss Landing, California 95039-9644
831-775-1766 (voice)
831-775-1620 (FAX)
***@mbari.org (email)
http://www.mbari.org (World-wide Web)

"The machine does not isolate man from the great mysteries
of nature, but plunges him more deeply into them."

- ANTOINE DE SAINT-EXUPERY
"Wind, Sand, and Stars" (1939)




------------------------------------------------------------------------------


_______________________________________________
omniORB-list mailing list
omniORB-***@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20070529/bfd53d0d/attachment-0001.htm
Duncan Grisby
2007-06-01 18:01:20 UTC
Permalink
Post by Tom O'Reilly
It seems that the error described below is connected to omniORB ipv6
support. I rebuilt and installed omniORB 4.1.0, after running
'configure' with the '--disable-ipv6' argument. Now 'omniNames -start'
runs without apparent error.
Is there some other way to solve this without disabling ipv6?
The issue is that your machine's libraries know about IPv6 but your
kernel doesn't, meaning that the configure script enables IPv6 support,
but it doesn't work. The best thing is to build without IPv6 support as
you have done.

You can force a server to only listen on IPv4 with an endPoint
specification of giop:tcp:0.0.0.0: . omniNames normally adds its own
endPoint specification, so you have to override that. You can run it
like this:

omniNames -start -ignoreport -ORBendPoint giop:tcp:0.0.0.0:2809

It's probably better to build omniORB without IPv6 though, otherwise
you'll have to do something similar for all servers.

Cheers,

Duncan.
--
-- Duncan Grisby --
-- ***@grisby.org --
-- http://www.grisby.org --
Loading...