My Oracle Support Banner

OID 12c Error: Failed to start instance oid1, Received error message from Node Manager Server: [Server start command for OID server 'oidX' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. (Doc ID 2345393.1)

Last updated on JANUARY 31, 2024

Applies to:

Oracle Internet Directory - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

Unable to start Oracle Internet Directory (OID) 12c:

Starting server oid1 ...
This Exception occurred
weblogic.nodemanager.NMException: Received error message from Node Manager Server: [Server start command for OID server 'oid1' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'oid1' log for detailed information.]. Please check Node Manager log for details.
Error: Error occurred while performing nmStart : Error Starting server oid1 : Received error message from Node Manager Server: [Server start command for OID server 'oid1' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'oid1' log for detailed information.]. Please check Node Manager log for details.
Use dumpStack() to view the full stacktrace :

Or, from wlst:

start(name='oid1',type='OID')
Traceback (innermost last):
 File "<console>", line 1, in ?
 File "<iostream>", line 1437, in start
 File "<iostream>", line 553, in raiseWLSTException
WLSTException: Error occurred while performing start : Please specify one of the following types: [Server|Cluster|SystemComponent|SystemComponentConfiguration]

Or, nodemanager.log with:

...<snip>...
<Jan 8, 2019 6:28:40 PM CET> <INFO> <Starting instance oid1.>
<Jan 8, 2019 6:28:40 PM CET> <WARNING> <Instance oid1 not found in DB>
<Jan 8, 2019 6:28:50 PM CET> <WARNING> <Failed to start instance oid1.>
<Jan 8, 2019 6:28:50 PM CET> <INFO> <Instance oid1 has changed state from STOPPED to FAILED>
<Jan 8, 2019 6:28:50 PM CET> <WARNING> <Server start command for OID server 'oid1' failed due to: [Failed to start instance oid1]. Please check Node Manager log and/or server 'oid1' log for detailed information.>
<Jan 8, 2019 6:34:19 PM CET> <INFO> <Starting instance oid1.>
<Jan 8, 2019 6:34:19 PM CET> <WARNING> <Instance oid1 not found in DB>
<Jan 8, 2019 6:34:29 PM CET> <WARNING> <Failed to start instance oid1.>
<Jan 8, 2019 6:34:29 PM CET> <INFO> <Instance oid1 has changed state from STOPPED to FAILED>
...<etc>...

And OID ldap server log (oidldapd01<pid>.log) with:

...<snip>...
[2019-01-09T10:06:51.174331+01:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: <HOSTNAME>] [pid: <PID>] [tid: <TID>] ServerDispatcher  : sgslufread: Hard error on read, OS error = 104
[2019-01-09T12:04:30.63728+01:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: <HOSTNAME>] [pid: <PID>] [tid: <TID>] [ecid: <ecid string>] ServerWorker (REG):[[
BEGIN
ConnID:464765 mesgID:2 OpID:1  OpName:search ConnIP:::ffff:<IP_ADDRESS>:xxxx ConnDN:Anonymous
sgslufread: Hard error on read, OS error = 32
END
]]
[2019-01-09T12:04:30.63812+01:00] [OID] [ERROR:8] [23199] [OIDLDAPD] [host: <HOSTNAME>] [pid: <PID>] [tid: <TID>] [ecid: <ecid string>] ServerWorker (REG):[[
BEGIN
 ConnID:464765 mesgID:2 OpID:1 OpName:search ConnIP:::ffff:<IP_ADDRESS>:xxxx ConnDN:Anonymous
In gsleswrrwRawWrite 0, writing to network failed due to hard or unknown error.
END
]]
[2019-01-09T13:07:53.308164+01:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: <HOSTNAME>] [pid: <PID>] [tid: <TID>] ServerDispatcher  : sgslufread: Hard error on read, OS error = 104
...<etc>...

Or:

$ ./startComponent.sh oid1
Starting system Component oid1 ...

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Reading domain from <$DOMAIN_HOME>

Please enter Node Manager password:
Connecting to Node Manager ...
<Apr 17, 2019 1:41:49 PM AST> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.>
<Apr 17, 2019 1:41:49 PM AST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<Apr 17, 2019 1:41:49 PM AST> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.>
Successfully Connected to Node Manager.
Starting server oid1 ...
This Exception occurred at Wed Apr 17 13:41:55 AST 2019.
weblogic.nodemanager.NMException: Received error message from Node Manager Server: [OID Server 'oid1' is either already running or in the process of starting/restarting]. Please check Node Manager log for details.
Error: Error occurred while performing nmStart : Error Starting server oid1 : Received error message from Node Manager Server: [OID Server 'oid1' is either already running or in the process of starting/restarting]. Please check Node Manager log for details.

Nothing more in the nodemanager.log and and oidmon/oidldapd logs are not updated at all.

The process status table has the process with a pid and state of 2, even though there was nothing running when grepping for oid*.

 

 Or:

Trying to bring down OID using command "./stopComponent.sh oid1" fails with:

Killing server oid1 ...
This Exception occurred at Mon Sep 13 07:24:35 EDT 2021.
weblogic.nodemanager.NMException: Received error message from Node Manager Server: [OID Server 'oid1' is not currently running]. Please check Node Manager log for details.
Error: Error occurred while performing nmKill : Error killing server oid1 : Received error message from Node Manager Server: [OID Server 'oid1' is not currently running]. Please check Node Manager log for details.

However, the oid process is still up:

 oracle  1184     1   0   Sep 10 ?           1:46 <path>/../bin/oiddispd connect=oiddb instance=1 inst=1  key=2047 host=<hostname>
 oracle  1186     1   0   Sep 10 ?          28:28 oidldapd     control=1184 connect=oiddb debug=0 configset=0 instance=1 key=2047 host=<hostname> logchange=TRUE port=<nonssl port> sport=<ssl port>

This could be due to the database was brought down before OID was brought down previously.

 

Changes

 

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
Changes
Cause
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.