EM 13c: Enterprise Manger 13c Cloud Control Oracle Management Service Startup Fails with Error: Java.io.FileNotFoundException: ./config/jps-config.xml (No Such File Or Directory)
(Doc ID 2355787.1)
Last updated on OCTOBER 19, 2019
Applies to:
Enterprise Manager Base Platform - Version 12.1.0.5.0 and laterInformation in this document applies to any platform.
Symptoms
Enterprise Manager (EM) 12.1.0.5.0 Cloud Control
Oracle Management Service (OMS) start
EM 12.1.0.5 Cloud Control OMS start fails with the following error concerning the WebLogic Server (WLS) Admin Server component:
#### <EMGC_ADMINSERVER> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> oracle.security.jps.JpsException: oracle.security.jps.config.JpsConfigurationException: ./config/jps-config.xml (No such file or directory)
at oracle.security.jps.wls.JpsWlsStartup.start(JpsWlsStartup.java:80)
at oracle.security.jps.JpsStartup.start(JpsStartup.java:109)
at oracle.security.jps.wls.JpsWlsStartupClass.main(JpsWlsStartupClass.java:39)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.security.jps.wls.JpsWlsStartup.start(JpsWlsStartup.java:80)
at oracle.security.jps.JpsStartup.start(JpsStartup.java:109)
at oracle.security.jps.wls.JpsWlsStartupClass.main(JpsWlsStartupClass.java:39)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
From the <OMS instance base>/gc_inst/NodeManager/emnodemanager/nodemanager.log:
<Oct 15, 2017 8:32:28 AM> <INFO> <Upgrade> <Saving upgraded node manager properties to '../gc_inst/user_projects/domains/GCDomain/nodemanage/nodemanager.properties'>
<Oct 15, 2017 8:32:28 AM> <SEVERE> <Fatal error in node manager server>
java.io.IOException: No space left on device
:
:
<Oct 15, 2017 8:44:49 PM> <INFO> <Loaded node manager configuration properties from '../gc_inst/user_projects/domains/GCDomain/nodemanage/nodemanager.properties'>
<Oct 15, 2017 8:44:49 PM> <INFO> <Upgrade> <Setting node manager properties version to 10.3>
<Oct 15, 2017 8:44:49 PM> <INFO> <Upgrade> <Saving upgraded node manager properties to '../gc_inst/user_projects/domains/GCDomain/nodemanage/nodemanager.properties'>
<Oct 15, 2017 8:32:28 AM> <SEVERE> <Fatal error in node manager server>
java.io.IOException: No space left on device
:
:
<Oct 15, 2017 8:44:49 PM> <INFO> <Loaded node manager configuration properties from '../gc_inst/user_projects/domains/GCDomain/nodemanage/nodemanager.properties'>
<Oct 15, 2017 8:44:49 PM> <INFO> <Upgrade> <Setting node manager properties version to 10.3>
<Oct 15, 2017 8:44:49 PM> <INFO> <Upgrade> <Saving upgraded node manager properties to '../gc_inst/user_projects/domains/GCDomain/nodemanage/nodemanager.properties'>
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 |