Failed to establish SSH connectivity to VM... Failed to start the service OR VM not accessible OR host unreachable via ping
Last updated on APRIL 06, 2018
Applies to:Oracle Database as a Service - Version N/A to N/A [Release 1.0]
Information in this document applies to any platform.
In this particular incident, user was configuring Corente VPN and might have made a mistake while doing that.
In a different incident, an instance can become inaccessible if a customer has created/attached a storage volume from Compute Portal and configured a fsck to run on the disk during boot in fsck. For example, if the sixth field for this storage volume is non-zero in /etc/fstab, then an fsck is attempted for this storage volume but since such storage volumes are not attached when the instance is rebooted, the instance goes into single user mode which is not accessible to customers. In this circumstance, the recommendation should be to not configure a fsck for storage volumes added from Compute Portal.
After an Oracle Cloud database instance shutdown, when trying to restart database instance it failed with this error message:
Failed to start the service [<SERVICE NAMR>]
In addition to that, Oracle Operations tried pinging the host private ip address and it failed with: Destination Host Unreachable.
Oracle Operations checked the Bridge interface for the VM and there was no communication seen, no RX packets.
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