Symantec Identity Suite - vApp machine is inaccessible, Error: "You are in rescue mode"

Products

• CA Identity Suite

Issue/Introduction

We are installing a new instance of the CA Identity platform in a separate data center.

After the VM image creation one of the Provisioning servers has become inaccessible. 

Error:

You are in rescue mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot into default mode.
Give root password for maintenance (or press Control-D to continue):

When that is used we only get a blank screen

 

Environment

Release : 14.4 and later

Resolution

New instance of vApp. After the VM image creation the PS was not accessible. As this is a new VM and it is in rescue mode, do you have enough disk space and memory allocation for this VM?  This would cause this type of rescue mode on a new VM.

Review and try increasing the disk space on the machine and also increase processors if you have the capacity? On boot, press Ctrl+D (if prompted) and the machine will boot, use the alias ResizeDisk to resize your hard disk, then reboot and confirm.

Here is the alias and documentation on this subject:

resizeDisk

Allows resizing the file-system size on the "/" volume after the Virtual Disk that is assigned to the Virtual Appliance Virtual Machine has been expanded in the host Virtualization platform.

Example: VMware ESX
The expansion operation in the host Virtualization platform typically requires shutting down the guest Virtual Machine.

 

Further information about the commands above see the document Available Aliases

Additional Information

This error can happen even when the VM is not newly deployed. The issue is caused by the disk space being completely consumed. First try increasing the disk space on the machine from the current size (Example 80) to an expanded size of 120. Then on boot, press Ctrl+D (if prompted), and the machine should boot, then use the alias ResizeDisk to resize your hard disk, then reboot. If successful then search the log file locations as it could be possible a log file grew too large and filled up the disk drive. This is most likely due to accidentally leaving Debug enabled on a specific component.