Exalogic Virtual: After Upgrading an Exalogic PSU, Proxy Control vServers (PC1, PC2) failed to Communicate to EC Control vServer
Last updated on OCTOBER 12, 2017
Applies to:Oracle Exalogic Elastic Cloud Software - Version 18.104.22.168.0 and later
Oracle Virtual Server (x86-64)
Post upgrade of an Exalogic PSU (e.g. Exalogic April 2017 PSU), vServer failed to start.
By reviewing the EMOC, irrespective of both Proxy Control vServers (PC1 and PC2) are running, they are shown as RED in EMOC.
PC2 Proxy Control vServer logs shows that there are issues with certificates:
- First Attempt of Exalogic PSU Patch 'EC Services' Upgrade
- 'EC Services' Upgrade failed during the phase of 'upgrade_java.sh script'
- Second Attempt of 'EC Services' Upgrade ran with the 're-run' command
- Since new EC certificate was already generated in first attempt, copying action was skipped => EC certificate was not copied to the PCs and 'Ec Services' upgrade finished successfully.
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