Oracle VM: Server Discovery Job Continues to be in Running state and Donot Progress
(Doc ID 2916735.1)
Last updated on DECEMBER 21, 2022
Applies to:
Oracle VM - Version 3.4.1 and laterInformation in this document applies to any platform.
Symptoms
Oracle VM Server(OVS) discovery job (command "discover_server") get stuck and continue to be in running state until the job is manually aborted.
Verified the following:
- connections to port "8899" & "7002" and it succeeds
- the gateway set is correct
- no issue with traceroute
- no issue with hostname resolution
- the "server discovery" job get stuck and never completes
Below are the only events when the discovery is initiated and there are no other events logged related to the discovery.
ovs-agent.log: [2022-11-28 15:15:48 21026] DEBUG (service:77) call start: get_api_version [2022-11-28 15:15:48 21026] DEBUG (service:77) call complete: get_api_version [2022-11-28 15:15:49 21027] DEBUG (service:77) call start: discover_server [2022-11-28 15:15:49 21027] DEBUG (service:77) call complete: discover_server adminserver.log: <BEA-000000> <Discovering server: ##.###.###.##> <BEA-000000> <Sending command: [get_api_version], to server: ##.###.###.##> <BEA-000000> <Server at IP address; ##.###.###.##. Supported versions: [6]> <BEA-000000> <Discovering [BASIC] data from server [null] address [##.###.###.##]> <BEA-000000> <Discovering server basic info. IP Address = ##.###.###.##> <BEA-000000> <Sending command: [discover_server], to server: ##.###.###.##>
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 |
References |