My Oracle Support Banner

OBIEE 12C - All OBIEE Services Down With Error Message: 'Could not connect to NodeManager' (Doc ID 2796625.1)

Last updated on AUGUST 06, 2021

Applies to:

Business Intelligence Server Enterprise Edition - Version 12.2.1.4.210402 and later
Information in this document applies to any platform.

Symptoms

You start OBIEE using $DOMAINHOME/bitools/bin/start.sh script

Nodemanager, Adminserver and bi server are running fine,

But all services are failed with below error message:

Server bi_server1 not started as already in state (RUNNING)
Starting obiccs1 (Original State:UNKNOWN) ...
Connection refused (Connection refused). Could not connect to NodeManager. Check that it is running at localhost/127.0.0.1:5556.
Starting obis1 (Original State:UNKNOWN) ...
Connection refused (Connection refused). Could not connect to NodeManager. Check that it is running at localhost/127.0.0.1:5556.
Starting obips1 (Original State:UNKNOWN) ...
Connection refused (Connection refused). Could not connect to NodeManager. Check that it is running at localhost/127.0.0.1:5556.
Starting obijh1 (Original State:UNKNOWN) ...
Connection refused (Connection refused). Could not connect to NodeManager. Check that it is running at localhost/127.0.0.1:5556.
Starting obisch1 (Original State:UNKNOWN) ...
Connection refused (Connection refused). Could not connect to NodeManager. Check that it is running at localhost/127.0.0.1:5556.
Failure to start one or more ManagedServers and or Components 

Cause

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
Symptoms
Cause
Solution


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