Jump to content
Kirti Jain

<OHS-0> <Failed to start the server ohs1>, Error: Error occurred while performing nmStart :

Recommended Posts

we successfully installed and configured OHS 12c in standalone mode also able to start node manager without any issue on 5556 port. After this when we start ohs1 our  system component getting below issue 

Error :

weblogic.nodemanager.NMException: Received error message from Node Manager Server: [Server start command for OHS server 'ohs1' failed due to: [Failed to start the server ohs1
Check log file /u01/app/oracle/sohsfmw/user_projects/domains/base_domain/system_components/OHS/ohs_nm.log]. Please check Node Manager log and/or server 'ohs1' log for detailed information.]. Please check Node Manager log for details.
Error: Error occurred while performing nmStart : Error Starting server ohs1 : Received error message from Node Manager Server: [Server start command for OHS server 'ohs1' failed due to: [Failed to start the server ohs1
Check log file /u01/app/oracle/sohsfmw/user_projects/domains/base_domain/system_components/OHS/ohs_nm.log]. Please check Node Manager log and/or server 'ohs1' log for detailed information.]. Please check Node Manager log for details. 
Use dumpStack() to view the full stacktrace :


Exiting WebLogic Scripting Tool.

Done

 

image.png.abd39c0479b41745388da838f36793a7.png

Share this post


Link to post
Share on other sites

[AK]  if you are in situation Like this and not able to start the system component check the logs first which shown in error in our case 

/u01/app/oracle/sohsfmw/user_projects/domains/base_domain/system_components/OHS/ohs_nm.log ,

 

and after reading the log the root cause of this issue as below :

image.png.8960dc14f71f357cb16749de31eb9143.png

 

check these two .conf file u01/app/oracle/sohsfmw/user_projects/domains/base_domain/config/fmwconfig/components/OHS/instances/ohs1/httpd.conf 

/u01/app/oracle/sohsfmw/user_projects/domains/base_domain/config/fmwconfig/components/OHS/instances/ohs1/ssl.conf:>
 

and the issue was with Listen address, we update the wrong listen address at the time of standalone configuration so we corrected the Listen address and then successfully able to start OHS Component.

 

image.png.c5152ed2cde0ddd5e43a632746a0ea28.png

 

 

 

 

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×