— Issue: Cannot start ohs after changing the node manager port.

[soaadmin@dcopppyots08 bin]$ ./startComponent.sh ohs1
Starting system Component ohs1 …

Initializing WebLogic Scripting Tool (WLST) …

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Reading domain from /app01/config/ohs_domain

Please enter Node Manager password:
Connecting to Node Manager …
This Exception occurred at Wed May 16 08:10:53 EDT 2018.
weblogic.nodemanager.NMException: Received error message from Node Manager Server: [Processing for domain ‘ohs_domain’ failed due to configuration error: [The domain ‘ohs_domain’ at ‘null’ was not registered in the nodemanager.domains file and dynamic domain registration is not supported. Please register the domain in the nodemanager.domains file.]]. 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: [Processing for domain ‘ohs_domain’ failed due to configuration error: [The domain ‘ohs_domain’ at ‘null’ was not registered in the nodemanager.domains file and dynamic domain registration is not supported. Please register the domain in the nodemanager.domains file.]]. Please check Node Manager log for details.
Use dumpStack() to view the full stacktrace :

— Solution:
— 1579149.1

— Edit $DOMAIN_HOME/config/config.xml and add the following line:

<listen-port>5557</listen-port>

to the node manager section.  Here 5557 is the modified port. You need to change to the port number of yours if it’s different. The updated section looks like this:

<node-manager>
<name>localmachine</name>
<listen-address>localhost</listen-address>
<listen-port>5557</listen-port>
<password-encrypted>{AES}vs3A2XWw1xx22YbzEbmv8pl0QPGawNC4gBzhBgZwhnY=</password-encrypted>
</node-manager>

3 Thoughts on “Cannot start ohs after changing the node manager port”

Leave a Reply

Your email address will not be published. Required fields are marked *