EM13c: REFRESH_FROM_MY_ORACLE_SUPPORT Job Failing "Timeout occurred while reading data from MOS"
(Doc ID 3040195.1)
Last updated on AUGUST 14, 2024
Applies to:
Enterprise Manager Base Platform - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
MOS Refresh job is failing with Timeout error while reading data from MOS.
OMS log reports below error during the MOS Refresh job run
<gc_inst>/em/EMGC_OMS1/sysman/log/emoms.trc
2024-08-05 12:42:53,610 [[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR login.MOSLoginCheckBean logp.251 - Unable to get MOSSession
oracle.sysman.emInternalSDK.core.mos.model.MOSException: 0:Read timed outEnvironment: [a.Protocol=https, b.Host Name=support.oracle.com, c.Port=443, d.Connection Timeout=180000 ms, e.Timeout=180000 ms, f.Proxy Host=<Proxy hostname /IP Address>, g.Proxy Port=<Proxy Port>, h.Path=/oauth/login, i.Parameters=[client-version=12.1.0.3, cmd=status, cmd-group=fwk, cmd-version=6.1, client-name=emmosadf]]
at oracle.sysman.emmos.mos.model.login.MOSLoginWorker.createMOSSession(MOSLoginWorker.java:117) ~[em-core-mos-model.jar:?]
at oracle.sysman.emmos.mos.ui.login.MOSHttpLoginWorker.performMOSLogin(MOSHttpLoginWorker.java:237) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.login.MOSHttpLoginWorker.performMOSLogin(MOSHttpLoginWorker.java:220) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.login.MOSHttpLoginWorker.doCreateMOSSession(MOSHttpLoginWorker.java:157) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.login.MOSHttpLoginWorker.doCreateMOSSession(MOSHttpLoginWorker.java:114) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.login.MOSHttpLoginWorker.getMOSSession(MOSHttpLoginWorker.java:101) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.facade.MOSHttpFacade.getMOSSession(MOSHttpFacade.java:123) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.adf.login.MOSLoginCheckBean.isLoggedIntoMOS(MOSLoginCheckBean.java:88) [em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.adf.login.MOSLoginCheckBean.getMOSLoginStatus(MOSLoginCheckBean.java:67) [em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.listener.MosAdfPhaseListener.loginCheck(MosAdfPhaseListener.java:248) [em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.listener.MosAdfPhaseListener.beforePhase(MosAdfPhaseListener.java:185) [em-core-mos-ui.jar:?]
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:345) [adf-richclient-impl-11.jar:ASPEN (custom: 12.2.1.4.42.190911.2248)]
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:270) [adf-richclient-impl-11.jar:ASPEN (custom: 12.2.1.4.42.190911.2248)]
oracle.sysman.emInternalSDK.core.mos.model.MOSException: 0:Read timed outEnvironment: [a.Protocol=https, b.Host Name=support.oracle.com, c.Port=443, d.Connection Timeout=180000 ms, e.Timeout=180000 ms, f.Proxy Host=<Proxy hostname /IP Address>, g.Proxy Port=<Proxy Port>, h.Path=/oauth/login, i.Parameters=[client-version=12.1.0.3, cmd=status, cmd-group=fwk, cmd-version=6.1, client-name=emmosadf]]
at oracle.sysman.emmos.mos.model.login.MOSLoginWorker.createMOSSession(MOSLoginWorker.java:117) ~[em-core-mos-model.jar:?]
at oracle.sysman.emmos.mos.ui.login.MOSHttpLoginWorker.performMOSLogin(MOSHttpLoginWorker.java:237) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.login.MOSHttpLoginWorker.performMOSLogin(MOSHttpLoginWorker.java:220) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.login.MOSHttpLoginWorker.doCreateMOSSession(MOSHttpLoginWorker.java:157) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.login.MOSHttpLoginWorker.doCreateMOSSession(MOSHttpLoginWorker.java:114) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.login.MOSHttpLoginWorker.getMOSSession(MOSHttpLoginWorker.java:101) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.facade.MOSHttpFacade.getMOSSession(MOSHttpFacade.java:123) ~[em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.adf.login.MOSLoginCheckBean.isLoggedIntoMOS(MOSLoginCheckBean.java:88) [em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.adf.login.MOSLoginCheckBean.getMOSLoginStatus(MOSLoginCheckBean.java:67) [em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.listener.MosAdfPhaseListener.loginCheck(MosAdfPhaseListener.java:248) [em-core-mos-ui.jar:?]
at oracle.sysman.emmos.mos.ui.listener.MosAdfPhaseListener.beforePhase(MosAdfPhaseListener.java:185) [em-core-mos-ui.jar:?]
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:345) [adf-richclient-impl-11.jar:ASPEN (custom: 12.2.1.4.42.190911.2248)]
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:270) [adf-richclient-impl-11.jar:ASPEN (custom: 12.2.1.4.42.190911.2248)]
You may experience slowness or hang while trying to access Patch Recommendation page in EM Console:
"Enterprise" -> "Provisioning and Patching" -> "Patches & Updates"
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 |
| Cause |
| Solution |
| References |