OTM 6.4.3 Installation Failed During the CreateOHS.py Script
(Doc ID 2466297.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Transportation Management - Version 6.4.3 and laterInformation in this document applies to any platform.
Symptoms
The OTM 6.4.3 the installation fails with the following errors in the < OTM Home >/logs/web_app_python_exec.log.
Tue Sep 18 09:51:49 EDT 2018
Start Running the CreateDomain.py script
Command executed /opt/bea_12.2.1.3.0/oracle_common/common/bin/wlst.sh <otm_home>/wlst/webapp/CreateDomain.py
Initializing WebLogic Scripting Tool (WLST) ...
Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Error: selectTemplate() failed. Do dumpStack() to see details.
Error: runCmd() failed. Do dumpStack() to see details.
Domain Creation Failed
None
Error: runCmd() failed. Do dumpStack() to see details.
Errors adding OHS to Domain
None
Exiting WebLogic Scripting Tool.
CreateDomain.py script completed: 0
Start Running the CreateDomain.py script
Command executed /opt/bea_12.2.1.3.0/oracle_common/common/bin/wlst.sh <otm_home>/wlst/webapp/CreateDomain.py
Initializing WebLogic Scripting Tool (WLST) ...
Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Error: selectTemplate() failed. Do dumpStack() to see details.
Error: runCmd() failed. Do dumpStack() to see details.
Domain Creation Failed
None
Error: runCmd() failed. Do dumpStack() to see details.
Errors adding OHS to Domain
None
Exiting WebLogic Scripting Tool.
CreateDomain.py script completed: 0
The log shows the following before failing.
The Node Manager is launched.
The Node Manager process is running independent of the WLST process.
Exiting WLST will not stop the Node Manager process. Please refer to the Node Manager logs for more information.
The Node Manager logs will be under /opt/bea_12.2.1.3.0/user_projects/domains/otm643/nodemanager
Launching Node Manager is completed.
Connecting to t3://<HostName>:<Port> with userid weblogic ...
This Exception occurred at Tue Sep 18 09:53:02 EDT 2018.
javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3://<HostName>:<Port>: Destination <IP Address>, <Port> unreachable.; nested exception is:
java.net.ConnectException: Connection refused (Connection refused); No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination. [Root exception is java.net.ConnectException: t3://<HostName>:<Port>: Destination <IP Address>, <Port> unreachable.; nested exception is:
java.net.ConnectException: Connection refused (Connection refused); No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.]
CreateOHS.py script completed: 1
The Node Manager process is running independent of the WLST process.
Exiting WLST will not stop the Node Manager process. Please refer to the Node Manager logs for more information.
The Node Manager logs will be under /opt/bea_12.2.1.3.0/user_projects/domains/otm643/nodemanager
Launching Node Manager is completed.
Connecting to t3://<HostName>:<Port> with userid weblogic ...
This Exception occurred at Tue Sep 18 09:53:02 EDT 2018.
javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3://<HostName>:<Port>: Destination <IP Address>, <Port> unreachable.; nested exception is:
java.net.ConnectException: Connection refused (Connection refused); No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination. [Root exception is java.net.ConnectException: t3://<HostName>:<Port>: Destination <IP Address>, <Port> unreachable.; nested exception is:
java.net.ConnectException: Connection refused (Connection refused); No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.]
CreateOHS.py script completed: 1
Note: The <HostName>, <Port> and <IP Address> will be for the server you are running the installation on.
--------------------------------------------------
This error is also noticed in the <Middleware 12.2.1.3 Home>/user_projects/domains/<OTM643 Domain>/nodemanager/nodemanager.log
<Sep 18, 2018 2:41:46 PM GMT> <INFO> <Loading domains file: /opt/bea_12.2.1.3.0/user_projects/domains/otm643/nodemanager/nodemanager.domains>
<Sep 18, 2018 2:41:46 PM GMT> <WARNING> <Domains file not found: /opt/bea_12.2.1.3.0/user_projects/domains/otm643/nodemanager/nodemanager.domains>
<Sep 18, 2018 2:42:21 PM GMT> <INFO> <Loading identity key store: FileName=/u01/bea_12.2.1.3.0/user_projects/domains/otm643/nodemanager/security/DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<Sep 18, 2018 2:42:21 PM GMT> <SEVERE> <Fatal error in NodeManager server>
weblogic.nodemanager.common.ConfigException: Identity key store file not found: /u01/bea_12.2.1.3.0/user_projects/domains/otm643/nodemanager/security/DemoIdentity.jks
at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.java:225)
at weblogic.nodemanager.server.SSLConfig.access$000(SSLConfig.java:33)
at weblogic.nodemanager.server.SSLConfig$1.run(SSLConfig.java:118)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:115)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:169)
at weblogic.nodemanager.server.NMServer.getInstance(NMServer.java:134)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:589)
at weblogic.NodeManager.main(NodeManager.java:31)
<Sep 18, 2018 2:41:46 PM GMT> <WARNING> <Domains file not found: /opt/bea_12.2.1.3.0/user_projects/domains/otm643/nodemanager/nodemanager.domains>
<Sep 18, 2018 2:42:21 PM GMT> <INFO> <Loading identity key store: FileName=/u01/bea_12.2.1.3.0/user_projects/domains/otm643/nodemanager/security/DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<Sep 18, 2018 2:42:21 PM GMT> <SEVERE> <Fatal error in NodeManager server>
weblogic.nodemanager.common.ConfigException: Identity key store file not found: /u01/bea_12.2.1.3.0/user_projects/domains/otm643/nodemanager/security/DemoIdentity.jks
at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.java:225)
at weblogic.nodemanager.server.SSLConfig.access$000(SSLConfig.java:33)
at weblogic.nodemanager.server.SSLConfig$1.run(SSLConfig.java:118)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:115)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:169)
at weblogic.nodemanager.server.NMServer.getInstance(NMServer.java:134)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:589)
at weblogic.NodeManager.main(NodeManager.java:31)
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 |