Starting OHS Fails With Error: Received error message from Node Manager Server: [Access to domain 'base_domain' for user 'weblogic' denied] if storeUserConfig Was Previously Used
(Doc ID 2580367.1)
Last updated on AUGUST 30, 2024
Applies to:
Oracle HTTP Server - Version 12.1.2.0.0 to 12.2.1.3.0 [Release 12c]Information in this document applies to any platform.
Symptoms
Attempting to start OHS using "startComponent.sh ohs_1"
the following error occurs.
$ startComponent.sh ohs_1
Starting system Component ohs_1 ...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Reading domain from DOMAIN_HOME
Connecting to Node Manager ...
This Exception occurred at Tue Jul 09 08:06:02 EDT 2019.
weblogic.nodemanager.NMException: Received error message from Node Manager Server: [Access to domain 'base_domain' for user 'weblogic' denied]. Please check Node Manager log for details.
Error: Error occurred while performing nmConnect : Cannot connect to Node Manager. : Received error message from Node Manager Server: [Access to domain 'base_domain' for user 'weblogic' denied]. Please check Node Manager log for details.
Use dumpStack() to view the full stacktrace :
Exiting WebLogic Scripting Tool.
Changes
When initially starting the OHS for the first time after installing/configuring, used the option storeUserConfig
DOMAIN_HOME/bin/startComponent.sh ohs_1 storeUserConfig
This is done so that when starting/stopping the OHS, the process will no longer request the nodemanager password to be input.
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 |