OVMAPI_4004E Server Failed Command: discover_server Status: exceptions TypeError:rpmdb open failed (Doc ID 1512465.1)

Last updated on MAY 23, 2017

Applies to:

Oracle VM - Version 3.0.3 to 3.1.1 [Release OVM30 to OVM31]
Information in this document applies to any platform.

Symptoms

  1. Symptom One: Server discovery under manager showing error: OVMAPI_4004E Server Failed Command: discover_server , Status: org.apache.xmlrpc.XmlRpcException: exceptions.TypeError:rpmdb open failed

    Job Construction Phase
    --------------------------
    begin()
    Appended operation 'Discover Manager Server Discover' to object 'OVM Foundry : Discover Manager'.
    commit()
    Completed Step: COMMIT

    Objects and Operations
    ----------------------
    Object (IN_USE): [DiscoverManager] OVM Foundry : Discover Manager
    Operation: Discover Manager Server Discover
    Object (IN_USE): [Server] 36:30:33:37:31:38:43:5a:33:31:32:39:4d:58:54:32 (ovs.oracle.com)

    Job Running Phase at 15:34 on Wed, Mar 27, 2013
    ----------------------------------------------
    Job Participants: []


    Actioner
    --------
    Starting operation 'Discover Manager Server Discover' on object 'OVM Foundry : Discover Manager'
    Setting Context to model only in job with id=1364384087160
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: discover_server to server: 192.168.0.10 failed. OVMAPI_4004E Server Failed Command: discover_server , Status: org.apache.xmlrpc.XmlRpcException: exceptions.TypeError:rpmdb open failed

    .....

    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: discover_server , Status: org.apache.xmlrpc.XmlRpcException: exceptions.TypeError:rpmdb open failed
    Wed Mar 27 15:34:47 GST 2013

  2. Symptom Two: On all Oracle VM servers in the server pool show a status of Running if operating properly. When a server remains in Starting status for an extended time, the status of server is likely abnormal.

    Below is a screenshot of the Oracle VM Manager showing this situation:

    Cause

    Sign In with your My Oracle Support account

    Don't have a My Oracle Support account? Click to get started

    My Oracle Support provides customers with access to over a
    Million Knowledge Articles and hundreds of Community platforms