ASAP Does Not Start Properly with a Ct_connect() Error in the CTRL Logs (Doc ID 1569495.1)

Last updated on AUGUST 07, 2016

Applies to:

Oracle Communications ASAP - Version 7.0.2 and later
Information in this document applies to any platform.

Symptoms

In ASAP Release R7_0_2/B166/SunOS environment:

1. Some of the ASAP servers (processes) are not starting after executing start_asap_sys -d command.

$ start_asap_sys -d
Starting Master Control Server CTRLPRO1...
Successful Startup of Master Control CTRLPRO1
Error : ASAP server is already running, or cannot start one of ASAP server

When we tried to start the remaining down (not started) servers, they start usually after one or two attempts for the case of NEP servers but the SARM usually takes several attempts to start.

Inside CTRLPRO1.diag we see messages like these:

CTRLPRO1: Msg 63 Layer 1 Origin 2 Severity 2
'ct_connect(): user api layer: internal Client Library error: Read from the server has timed out.'
CTRLPRO1: Msg 4 Layer 5 Origin 3 Severity 5
'ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed'
'Socket connect failed - errno 146 Connection refused'
Killing Java Interpreter JNP03PRO1 (Generic JNP03PRO1), Pid 1857

The problem does not seem to be related to any particular ASAP server and the problem seems to occur in random ASAP servers and sometimes the problem does not show up and ASAP starts up apparently without any problems. The problem occurs mostly on SARM server but the problem is with NEPs and SRP servers too. When we tried starting each server with 'starts –d' command and even without starting the SARM server some of the other NEP servers fail to start at some point.

Current configuration of ASAP has 13 NEP servers, 130 NEs and 1609 devices. ASAP.cfg, ASAP.properties and Environment_profile files have been configured according to Administration Guide specifications.

The kernel and database configurations parameters are according to Administration Guide and have been either meet or exceeded all the requirements.

2. We can see the following message in ASAP.Console when enabling pre emptive on NEP servers:

NP02PRO1: Resetting PRE_EMPTIVE to FALSE for a non SARM server.

However in NEP diags we can see it is still enabled:

PRE_EMPTIVE          : TRUE                                Configurable: Yes

Changes

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms