My Oracle Support Banner

Oracle VM: After Restoring MySQL Database, Log in to Oracle VM Manager fails with Error "Unable to connect to core. Retrying in 30 seconds" (Doc ID 1929070.1)

Last updated on FEBRUARY 01, 2024

Applies to:

Oracle VM - Version 3.3.1 to 3.3.4 [Release OVM33]
Oracle Cloud Infrastructure - Version N/A and later
Linux x86-64

Symptoms

In Oracle VM release 3.3.1, after restoring MySQL DB, Log in to Oracle VM manager UI failed.

Below is the error snippet captured in AdminServer.log

####<2014-09-04T04:29:33.157+0200> <Warning> <com.oracle.ovm.appfw.db.Synchronizer> <ovmm33> <AdminServer> <Thread-36> <> <> <6ffd5a25-5d73-4c2f-899b-268107d4d0b2-00000003> <1409797773157> <BEA-000000> <Unable to connect to core. Retrying in 30 seconds.>  

####<2014-09-04T04:30:04.061+0200> <Error> <com.oracle.ovm.appfw.coreinterface.ConnectionManager> <ovmm33> <AdminServer> <Thread-36> <> <> <6ffd5a25-5d73-4c2f-899b-268107d4d0b2-00000003> <1409797804061> <BEA-000000> <AppFw session 1: Failed to connect to Web Service API. 

...
####<2014-09-04T04:30:04.062+0200> <Warning> <com.oracle.ovm.appfw.db.Synchronizer> <ovmm33> <AdminServer> <Thread-36> <> <> <6ffd5a25-5d73-4c2f-899b-268107d4d0b2-00000003> <1409797804062> <BEA-000000> <Unable to connect to core. Retrying in 30 seconds.> 

 

 

Changes

 The Oracle VM Manager was Reinstalled with old UUID and then the DB was restored.

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


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