On Saturday 14 February 2009 00:15:57 Peter Soetens wrote:
>
> $ Naming_Service
> (23488|140573463234288) EXCEPTION, TAO_Naming_Server::init_with_orb
> system exception, ID 'IDL:omg.org/CORBA/INTERNAL:1.0'
> TAO exception, minor code = 0 (endpoint initialization failure in Acceptor
> Registry; unspecified errno), completed = NO
>
> Failed to start the Naming Service.
>
> Any ideas ?

I didn't have the ipv6 kernel module loaded, while ACE/TAO was compiled with
ipv6 support enabled. Annoying.

Peter

On Feb 13, 2009, at 18:15 , Peter Soetens wrote:

> When running the unit tests and having configured for TAO, I get this
> exception:
>
> 80.264 [ Info ][./tests/corba-test::main()] Creating new
> ControlTaskServer
> for root
> 90.274 [ ERROR ][./tests/corba-test::main()] CORBA exception raised!
> 90.275 [ ERROR ][./tests/corba-test::main()] system exception, ID
> 'IDL:omg.org/CORBA/INTERNAL:1.0'
> TAO exception, minor code = 0 (endpoint initialization failure in
> Acceptor
> Registry; unspecified errno), completed = NO
>
> It looks like a network configuration problem, although my network
> is plugged
> in and operational. Omniorb works fine. Some googling gave very little
> solutions. When starting the TAO Naming_Service, I get the same
> exception, so
> it's not Orocos specific:
>
> $ Naming_Service
> (23488|140573463234288) EXCEPTION, TAO_Naming_Server::init_with_orb
> system exception, ID 'IDL:omg.org/CORBA/INTERNAL:1.0'
> TAO exception, minor code = 0 (endpoint initialization failure in
> Acceptor
> Registry; unspecified errno), completed = NO
>
> Failed to start the Naming Service.
>
> Any ideas ?

I get this same erro if I try to start the naming service with a FQDN
(ie a network interface on this host) and not an IP address. Might no
parameters cause a host lookup underneath, that fails?

S