1/29/2020 Document 2245197.
1
Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.
OVM 3.4.1: OVM Manager showing the Oracle VM Server status as "Starting" although it is
running (Doc ID 2245197.1)
In this Document
Symptoms
Changes
Cause
Solution
APPLIES TO:
Oracle VM - Version 3.4.1 and later
Linux x86-64
SYMPTOMS
Few of the OVM server in the pool went to "Starting" status in OVM manager automatically without any manually
intervention although it was running and we were able to ssh the server .
The ovs-agent.log be like :
[2016-12-20 09:58:12 4978] INFO (xmlrpc:426) Error reloading XMLRPC Server: [Errno 9] Bad file
descriptor <<==========
[2016-12-20 09:58:12 4978] DEBUG (xmlrpc:291) Manager cert subject: [('C', 'US'), ('ST',
'California'), ('L', 'Redwood City'), ('O', 'Oracle'), ('OU', 'Oracle VM Manager'), ('CN',
'0004fb0000010000f910759d60662e5f')]
[2016-12-20 09:58:12 4978] DEBUG (xmlrpc:292) Manager cert issuer: [('C', 'US'), ('ST',
'California'), ('L', 'Redwood City'), ('O', 'Oracle'), ('OU', 'Oracle VM Manager'), ('CN',
'0004fb0000010000f910759d60662e5f')]
[2016-12-20 09:58:12 4978] INFO (xmlrpc:422) Oracle VM Agent XMLRPC Server started.
[2016-12-20 09:58:13 21789] DEBUG (service:75) call start: update_server_roles('utility,xen',)
[2016-12-20 09:58:13 21789] DEBUG (service:77) call complete: update_server_roles
[2016-12-20 09:58:14 21790] DEBUG (service:75) call start: package_list('updates',)
[2016-12-20 09:58:14 21790] DEBUG (service:77) call complete: package_list
[2016-12-20 09:58:18 21846] DEBUG (service:77) call start: get_api_version
Then the ovs-agent and the ovmm services were restarted but with no luck. The server was then tried to refresh from the
OVM CLI as the option of re-discover was greyed out
OVM> refresh server name=ovs.server.local
Command: refresh server name=ovs.server.local
Status: Failure
Time: 2017-03-16 10:26:47,642 CDT
JobId: 1489678006939
Error Msg: Job failed on Core: OVMAPI_6000E Internal Error: OVMAPI_4021E Server discover conflict
at IP address: x.x.x.x. The manager already has a server: ovs.server.local, at this IP address,
with SMBIOS UUID: 00:25:90:fa:6d:14:00:25:90:fa:6d:15:0c:c4:7a:58.
CHANGES
No changes
CAUSE
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=ovbaltpb_4&id=2245197.1 1/2
1/29/2020 Document 2245197.1
This can happen in the below cases :
1) This server has the same IP address as another server.
2) The SMBIOS UUID of this server has changed due to a server motherboard change.
3) The SMBIOS UUID has changed due to moving the blade in the chassis and there is an incorrect blade chassis SMBIOS
UUID setting which allows the UUID of the server to change with the slot.
SOLUTION
1 ) Get the OVM server UUID from OVM manager Under the Advance section by choosing the perspective as "Info"
Now add the UUID to the file /etc/ovs-agent/agent.ini on Oracle VM server to the starting with "fakeuuid" line as there
was no UUID present:
# cat /etc/ovs-agent/agent.ini
...snip...
[server]
fakeuuid= 44:45:4c:4c:54:00:10:4e:80:48:c3:c0:4f:4a:48:31
2) Started the ovs-agent services of the OVM server :
# service ovs-agent restart
3 ) a. Login to CLI from the manager server
#ssh admin@localhost -p 10000
b. List the servers and then do a refresh
OVM> list server
OVM> refresh server name=<Name of server found by "list server" command>
The starting status of the server will change to "Running"
Didn't find what you are looking for?
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=ovbaltpb_4&id=2245197.1 2/2
