My Oracle Support Banner

Oracle VM: Unable to Start Oracle VM Manager Service (ovmm) as It's Getting Shutting Down While Starting (Doc ID 2370797.1)

Last updated on JULY 27, 2023

Applies to:

Oracle Cloud Infrastructure - Version N/A and later
Oracle VM - Version 3.2.1 and later
Linux x86-64

Symptoms

Fails to start the ovmm service as its getting shutting down while starting. But Mysql DB is started fine after starting ovmm.

You can see below errors in AdminServer.log file:

####<Feb 9, 2018 4:40:28 AM CST> <Info> <Store> <ovmm> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <><1518172828921> <WL-280008>
<Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/data/store/diagnostics requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".>
####<Feb 9, 2018 4:40:28 AM CST> <Critical> <WebLogicServer> <adc57ovmm02.oracle.com> <AdminServer> <main> <> <> <> <1518172828925> <WL-000386> <Server subsystem failed. Reason:
java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.store.io.file.StoreFile.close(StoreFile.java:440)
at weblogic.store.io.file.Heap.open(Heap.java:320)
at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:104)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:431)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:422)
at weblogic.store.xa.PersistentStoreManagerXA.createFileStore(PersistentStoreManagerXA.java:117)
at weblogic.diagnostics.archive.DiagnosticStoreRepository.getStore(DiagnosticStoreRepository.java:91)
at weblogic.diagnostics.lifecycle.DiagnosticSystemService.start(DiagnosticSystemService.java:143)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Feb 9, 2018 4:40:28 AM CST> <Notice> <WebLogicServer> <ovmm> <AdminServer> <main> <> <> <> <1518172828927> <WL-000365> <Server state changed to FAILED>
####<Feb 9, 2018 4:40:28 AM CST> <Error> <WebLogicServer> <ovmm> <AdminServer> <main> <> <> <> <1518172828928> <WL-000383> <A critical service failed. The server will shut itself down>
####<Feb 9, 2018 4:40:28 AM CST> <Notice> <WebLogicServer> <ovmm> <AdminServer> <main> <> <> <> <1518172828929> <WL-000365> <Server state changed to FORCE_SHUTTING_DOWN>


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.