NFS Archive Location Mount Fails

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Login to Aria Operations for Logs UI. Expand the main menu, select Log Management and then click Index Partitions.
Edit the index partition, Click Test to verify the connection with the NFS storage.
Test fails with "Failed" message as shown below:
In /var/log/vmware/loginsight/runtime.log file you see below error:

[xxxx-xx-xx 11:24:18.389+0000] ["ArchivingTasksHandler-thread-1"/xx.xx.xx.xx INFO] [com.vmware.loginsight.commons.executor.ProcessExecutor] [Finished executing mount nfs_host:/nfs_path /storage/core/loginsight/nfsmount/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx, ran for 272 ms]
[xxxx-xx-xx 11:24:18.389+0000] ["ArchivingTasksHandler-thread-1"/nfs_host ERROR] [com.vmware.loginsight.commons.FileUtils] [Failed to run 'mount nfs_host:/nfs_path /storage/core/loginsight/nfsmount/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx ' exitCode=32 stdout='' stderr='mount.nfs: mount point /storage/core/loginsight/nfsmount/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx does not exist]
[xxxx-xx-xx 11:24:18.389+0000] ["ArchivingTasksHandler-thread-1"/nfs_host ERROR] [com.vmware.loginsight.repository.RepositoryWriter] [Failed to archive bucket xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx]
java.io.IOException: Failed to mount NFS archive location.

Environment

VMware Aria Operations for Logs 8.x

Cause

This issue occurs when the 'nfsmount' folder is full, which prevents new mounting points from being created.

Resolution

To resolve this issue, remove all unmounted directories from the 'nfsmount' folder.

Remove Unmounted Directories:

Delete all unmounted directories from the nfsmount folder using the command below:

Note: This command must be run on all nodes in the Aria Operations for Logs cluster.

If the above troubleshooting steps do not resolve the issue, consider following below options:

Option 1: Configure NFS Version 3 for Li Service

1. Create a file /etc/nfsmount.conf with the following options:

[Server "<nfs_fqdn>"]
vers=3
proto=tcp

2. Verify that the NFS share mounts available without specifying extra options.
3. Copy the nfsmount.conf file to other worker nodes.
4. Enable NFS archival from the UI and test the connection.

Rationale:
This configuration forces the Li service to use NFS version 3, which has been confirmed to work through manual testing. By specifying the NFS version, you can ensure a stable connection to the NFS share and prevent issues with stale buckets and manual mounting.

Expected Outcome:
After implementing this configuration, NFS archival should work successfully, and the test connection should return success.