Discussion:
[omniORB] NamingService exception
Natalia Olano
2009-01-13 22:45:02 UTC
Permalink
Hello,

I installed omniORB-4.1.2 and omniORBpy-3.2 to be used with a third
party application. There was no error message during the installation,
but when I try to run the NamingService like:

/usr/bin/Naming_ServiceDaemon -d -ORBEndPoint iiop://hostname:50001

I get the following exception:

(24028|3076495040) EXCEPTION, TAO_Naming_Server::init_with_orb
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 6 (endpoint initialization failure in
Acceptor Registry; ENOENT), completed = NO

Failed to start the Naming Service.

I have seen the application running in the same configuration it is
now and I have not found information on this error, so I would really
appreciate some help.

Thanks!
--
N. Olano
Duncan Grisby
2009-01-14 00:23:37 UTC
Permalink
Post by Natalia Olano
I installed omniORB-4.1.2 and omniORBpy-3.2 to be used with a third
party application. There was no error message during the installation,
/usr/bin/Naming_ServiceDaemon -d -ORBEndPoint iiop://hostname:50001
(24028|3076495040) EXCEPTION, TAO_Naming_Server::init_with_orb
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 6 (endpoint initialization failure in
Acceptor Registry; ENOENT), completed = NO
That is nothing to do with omniORB. It's part of TAO, which is a
completely different C++ CORBA implementation.

omniORB's naming service is called omniNames.

Cheers,

Duncan.
--
-- Duncan Grisby --
-- ***@grisby.org --
-- http://www.grisby.org --
Michael
2009-01-14 05:58:08 UTC
Permalink
This is not omniORBs naming service omniNames but TAO's naming service.
Either wrong software or wrong mailing list :)
Post by Natalia Olano
Hello,
I installed omniORB-4.1.2 and omniORBpy-3.2 to be used with a third
party application. There was no error message during the installation,
/usr/bin/Naming_ServiceDaemon -d -ORBEndPoint iiop://hostname:50001
(24028|3076495040) EXCEPTION, TAO_Naming_Server::init_with_orb
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 6 (endpoint initialization failure in
Acceptor Registry; ENOENT), completed = NO
Failed to start the Naming Service.
I have seen the application running in the same configuration it is
now and I have not found information on this error, so I would really
appreciate some help.
Thanks!
Natalia Olano
2009-01-14 14:09:55 UTC
Permalink
Thanks for pointing me in the right direction :)
Post by Michael
This is not omniORBs naming service omniNames but TAO's naming service.
Either wrong software or wrong mailing list :)
Post by Natalia Olano
Hello,
I installed omniORB-4.1.2 and omniORBpy-3.2 to be used with a third
party application. There was no error message during the installation,
/usr/bin/Naming_ServiceDaemon -d -ORBEndPoint iiop://hostname:50001
(24028|3076495040) EXCEPTION, TAO_Naming_Server::init_with_orb
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 6 (endpoint initialization failure in
Acceptor Registry; ENOENT), completed = NO
Failed to start the Naming Service.
I have seen the application running in the same configuration it is
now and I have not found information on this error, so I would really
appreciate some help.
Thanks!
--
Natalia Olano Ag?ero
Loading...