My Oracle Support Banner

What Can Cause the Naming Service to Fail and Prevent it From Restarting ? (Doc ID 2674816.1)

Last updated on MAY 28, 2020

Applies to:

Oracle Utilities Network Management System - Version 2.3.0.2.0 and later
Oracle Network Management for Utilities - DMS - Version 2.3.0.2.0 and later
Information in this document applies to any platform.

Goal

Q1: What could cause the naming service to crash?

 

Q2: What can cause the naming service (tao_cosnaming) to fail to start with this error?

TAO (17342|140035940124480) - IIOP_Acceptor::open, address==<SERVER>:<PORT>, options=(null)
TAO (17342|140035940124480) - IIOP_Acceptor::open, specified host=<SERVER>:<PORT>
TAO (17342|140035940124480) - IIOP_Acceptor::open_i, trying to listen on port <PORT>
TAO (17342|140035940124480) - IIOP_Acceptor::open_i, cannot open acceptor in port range (<PORT>,<PORT>)- : Address already in use
TAO (17342|140035940124480) - Unable to open acceptor for <>: Address already in use
ACE (17342|140035940124480) SCG:<dtor=0x7ffe5eadb210> - new repo=0xd3c660
(17342|140035940124480) EXCEPTION, TAO_Naming_Server::init_with_orb
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'

 

 

Q3: What can cause the this error?

ACE (17342|140035940124480) STDG::<ctor>, repo=0xd3c660, name=./svc.conf - beginning at [63]
ACE (17342|140035940124480): ./svc.conf: No such file or directory
ACE (17342|140035940124480) STDG::<dtor> - Failed (-1) to find ./svc.conf -> (nil)
TAO (17342|140035940124480) - Did not find default svc.conf
TAO (17342|140035940124480) - Completed initializing the process-wide service context
TAO (17342|140035940124480) - Default ORB services initialization begins

 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.