Exachk Not Doing Health Checks On Compute Nodes and Control vServers in Exalogic Virtual Environments, reporting : No failed checks reported; review "Killed Processes" and / or "Skipped Checks
Last updated on JANUARY 23, 2015
Applies to:Oracle Exalogic Elastic Cloud Software - Version 18.104.22.168.2 and later
Oracle Virtual Server (x86-64)
In Exalogic Virtual environments issue of Exachk not doing the checks on the Compute Nodes and Control vServer is observed.
When looking at the Exachk output HTML file generated by Exachk execution we see "No failed checks reported; review "Killed Processes" and / or "Skipped Checks"" messages as shown in following screenshot.
In this case the there were no issues with the Exachk configuration. All the Compute Node & Control Stack vServer Hostnames were reachable from the EMOC EC1 vServer from which Exachk was being executed
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