- HTTP 404 Error accessing gateway
- Service-va logs show something similar to
com.vmware.horizon.analytics.exception.HorizonException: Setting up Message Broker connection failed: Connection refused - Running df -h on the service-va shows /db as full
Cause
The internal Postgres Database is full and must be expanded. This article does not apply to Workspace implementations that have an external database configured.
Resolution
To resolve this issue, add a new, large VMDK to the service-va and copy the contents from the old disk to the new one. This process works on service-va VMs with and without internet access.
- Take a snapshot of the service-va
- Power off the Workspace vApp
- Add a VMDK to the service-va
3a. Right click the service-va and choose Edit Settings > Add > Hard Disk and choose Create new virtual disk
3b. Ensure the new disk is at least 30GB in size - Power on the service-va VM only and login as root
- Change to run level 1
init 1
5a. Verify you are in Run Level 1 by typing who -r - Determine the name of the new disk (e.g., /dev/sdxx)
fdisk -l - Format the new disk with default parameters
fdisk /dev/sdxx
n (for new partition)
p (for primary partition)
Press Enter to accept Partition Number Default
w (to write changes) - Unmount /db (first take note of the device name, e.g., /dev/sdb1)
umount /db - Copy the contents of /db (in this example, /dev/sdb1) to the new partition
dd if=/dev/sdb1 of=/dev/sdxx bs=1024
NOTE: This copy operation may take a long time - Resize the filesystem using resize2fs
e2fsck -f /dev/sdxx
resize2fs /dev/sdxx - Mount /dev/sdb1 to /db
mount /dev/sdb1 /db - Update /etc/fstab to reflect the new partition mounted at /db
- Run this command to shutdown the service-va
shutdown -h now - Power on the Workspace vApp.
NOTE: be sure to commit the snapshot previously taken after verifying the environment is stable
0 comments:
Post a Comment