Oracle VM Manager: OVMAPI_6000E Internal Error: Connection Refused

May 16, 2012 / By Yury Velikanov

Tags: , ,

This is just a quick post to share my first 3.1.1 Oracle VM Manager (OVMM) troubleshooting experience.

After the initial installation, I rebooted the server, tried to access OVMM https://ovmmhost:7002/ovm/console, and received the following error in a browser screen:

Unexpected error during login (com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6000E Internal Error: Connection refused Connection refused[[ < date > ), please consult logs for details. OVMAPI_6000E Internal Error: Connection refused Connection refused
< date >
Unexpected error during login (com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6000E Internal Error: Connection refused Connection refused[[ < date > ), please consult logs for details. OVMAPI_6000E Internal Error: Connection refused Connection refused date .

If you see that error and try looking for a solution on Google, then unfortunately for you it is a very generic error message (a.k.a. ORA-600 in Oracle VM world ;) ) and you will need to dig a bit to find out what exactly is wrong in your case. For me, the system time had been changed for a reason or another, and OVMM refused to accept it. How did I find it? The answer is as follows.

[root@team5lab ~]# grep -i "error"  /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/logs/AdminServer*
/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/logs/AdminServer-diagnostic.log:[2012-05-15T06:10:51.068-04:00] [AdminServer] [ERROR] [] [org.apache.myfaces.trinidadinternal.application.StateManagerImpl] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 5901ed0250b40ee9:-7b25700f:1374ff71fa3:-8000-0000000000000019,0] [APP: ovm_console] Could not find saved view state for token -7fm4vgxvd
/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/logs/AdminServer-diagnostic.log:[2012-05-15T06:12:29.507-04:00] [AdminServer] [ERROR] [] [com.oracle.ovm.mgr.faces.backing.Login] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 5901ed0250b40ee9:-7b25700f:1374ff71fa3:-8000-000000000000002d,0] [APP: ovm_console] Unexpected error during login (com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6000E Internal Error: Connection refused Connection refused[[
/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/logs/AdminServer-diagnostic.log:Tue May 15 06:12:29 EDT 2012), please consult logs for details. OVMAPI_6000E Internal Error: Connection refused Connection refused
/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/logs/AdminServer.log:wlw.logErrorsToConsole = false
/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/logs/AdminServer.log:                   FATAL ERROR: THE CURRENT SYSTEM TIME IS EARLIER THAN THE MOST RECENT EVENT TIME IN OVM MANAGER!
/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/logs/AdminServer.log:####     <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <0000JTFxnHv9h^WjLxbQ8A1FgYf8000002> <1337076450944>
[root@team5lab ~]#

From the output “FATAL ERROR: THE CURRENT SYSTEM TIME IS EARLIER THAN THE MOST RECENT EVENT TIME IN OVM MANAGER!”, the problem was clear. I just checked the system time and fixed it.

Just to save you some googling time:

####      <>   <Received exception while creating connection for pool “OVMDS”: ORA-28000: the account is locked

Solution (Avi Miller)

####      <>    <Workflow Manager: , com.oracle.odof.command.InvokeMethodCommand@5f46b669
java.lang.OutOfMemoryError: Java heap space

Solution (Avi Miller)

General peace of advice: If you’re stuck with an Oracle VM issue, look for Avi Miller in OTN Oracle VM Forums. He is the man. ;)

One Response to “Oracle VM Manager: OVMAPI_6000E Internal Error: Connection Refused”

  • Ravi Kasibhatla says:

    Hi,

    we have an atypical issue with the OVM environment that was stable for almost an year.
    Sincea few days the below issue is presenting and we can’t find a reason for that. Any help in the regard is greatly appreciated.

    – 4 of the blades with OVM Server are up and running with their respective VMs
    – but when we try to start the OVM Manager service, that is on a separate blade, all the OVM Server blades are coming down one-by-one except the OVM Master server.
    – The log on each OVM Server that goes down shows clean shutdown process without any error messages, but we couldn’t find why the shutdown (init0 ) signal was sent to them and who send them (either manager or the master)

    Any insight into the issue would be a great help.

    Regards

    Ravi

Leave a Reply

  • (will not be published)

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>