Resolution when Automation Suite installer fails with: "Mount Path not exposed for nfs server"
Issue Description:
Automation Suite installer fails with "Mount Path not exposed for NFS server".
Root Cause:
This error means that the NFS server is reachable (there is a prerequisite check before this step to verify that) but that the specified file path is not available.
Resolution:
- The installer will show this error when the following command fails:
- mount -t nfs :
- corresponds to the NFS IP or DNS. For 22.4 and below this is defined in the backup.json as the NFS endpoint (backup.nfs.endpoint)
- corresponds to the directory from the NFS endpoint to be mounted. For 22.4 and below this is defined in the backup.json as the mount point (backup.json.mountpath)
- corresponds to the directory on the localhost. The script generates this and its value by default is /mnt/backup
- This error will most likely occur when using an existing NFS server.
- If this is a new NFS, set the to '/'. Or if preferred, create the directory name by following the below steps.
- When this error is encountered, the correct NFS mounting dir needs to be created. These are steps that can be used to do that. These commands should be run on a server with access to the NFS server.
- mkdir -p /mnt/tmp
- mount -t nfs :/ /mnt/tmp
- Once it is mounted, either query the mount point for the correct name or make the name that is needed.
- To see the directories on the mount point, run: ls -lrt /mnt/tmp
- To make the needed directory at the root level run: mkdir /mnt/tmp/
- i.e. mkdir /mnt/tmp/asbackup
- To unmount the directory run: umount /mnt/tmp
- Once the directory is created or the proper path is determined run the following commands to verify that the is not mountable
- mount -t nfs : /mnt/tmp
- umount /mnt/tmp
- Re-run the backup configuration script.
- If the mount command fails, capture the error and raise a UiPath Support ticket.