vRealize Automation appliance runs out of disk space
search cancel

vRealize Automation appliance runs out of disk space

book

Article ID: 318334

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
The VMware vRealize Automation appliance with an embedded vPostgres database experiences low disk space.

Environment

VMware vRealize Automation 7.x

Resolution

To increase the available disk space:
  1. Shut down the VMware vRealize Automation appliance.
  2. Add a new hard disk to the vRealize Automation appliance.

    For more information on adding a new hard disk, see:
  3. Power on the appliance.
  4. Connect to the appliance using SSH.
  5. List all disks and identify the device ID of the new disk added by running this command in the shell client:

    fdisk -lu

    Note: By default, the device ID for the new disk is /dev/sdc or /dev/sde. This device name is generated based on your existing devices and could be a different letter in the name.
  6. Access the disk utility for the new disk:
    1. Run this command

      fdisk /dev/sdc
       
    2. Press N then press Enter for new partition.
    3. Press P then press Enter for primary partition.
    4. Press 1 as the partition number.
    5. Accept the default start block and the default end block.
    6. Press W to write the partition table to disk.
    7. Create a new partition on the new disk.
  7. Create an ext3 file system on the new disk using this command:

    mkfs -t ext3 /dev/sdc1
     
  8. Create a new temporary directory under the root directory by running this command:

    mkdir /tmp/db
     
  9. Mount the new disk to the /tmp/db directory by running this command:

    mount -t ext3 /dev/sdc1 /tmp/db
     
  10. Power off all services that access the vPostgres /storage/db directory by running these commands:
vRealize Automation 6.x Only:
service apache2 stop
 
vRealize Automation 7.x Only:
service elasticsearch stop

vRealize Automation 7.5+ Only:
Note! Ensure psql-manager is stopped in 7.5+ before stopping vpostgres
service psql-manager stop

All Versions:
service vcac-server stop
service vco-server stop
service vpostgres stop
  1. Copy all the /storage/db files into the /tmp/db directory by running this command:

    cp -a /storage/db/* /tmp/db
  2. Return to the root directory by running this command:

    cd /
  3. Verify the mount points by running this command:

    mount

    You see output similar to:

    /dev/sda1 on / type ext3 (rw)
    proc on /proc type proc (rw)
    sysfs on /sys type sysfs (rw)
    udev on /dev type tmpfs (rw,mode=0755)
    tmpfs on /dev/shm type tmpfs (rw,mode=1777)
    devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
    /dev/sdb1 on /storage/log type ext3 (rw,nosuid,nodev)
    /dev/sdb2 on /storage/db type ext3 (rw,nosuid,nodev)
    /dev/sdc1 on /tmp/db type ext3 (rw)
  4. Unmount the original disk and the new disk by running these commands:

    umount /dev/sdb2
    umount /dev/sdc1
  5. Mount the new disk to the /storage/db directory by running this command:

    mount -t ext3 /dev/sdc1 /storage/db
  6. Preserve the new mount to the /storage/db directory by running the command:

    sed -i -e 's#/dev/sdb2#/dev/sdc1#' /etc/fstab
  7. Restart the appliance.

Note: These steps are specific to the SDB2 partition that holds the vPostgres database. To increase the disk space in other partitions, update the commands to match the correct location. If you need additional support, contact VMware support.

For more information, see Filing a Support Request in Customer Connect (2006985) or How to Submit a Support Request.


Powered by Wolken Software