This section contains basic NFS server troubleshooting for the Abiquo platform
Check the NFS configuration is correct on the remote services server
Check that your config file has the correct settings for your NFS share. Assuming your NFS Server has the IP address 192.168.1.10. The entries for nfs in file /opt/abiquo/config/abiquo.properties should look like the example below.
abiquo.appliancemanager.localRepositoryPath = /opt/vm_repository/ abiquo.appliancemanager.repositoryLocation = 192.168.1.10:/opt/vm_repository abiquo.virtualfactory.hyperv.repositoryLocation = //192.168.1.10/vm_repository abiquo.virtualfactory.xenserver.repositoryLocation = 192.168.1.10:/opt/vm_repository
If you make any changes to the abiquo.properties file, remember to restart the Abiquo Tomcat server
Check the NFS repository is mounted
After you install the Abiquo platform, check that the NFS Repository is mounted on the Abiquo Remote Services host and the Abiquo V2V Services host (See VM repository folder).
Assuming your NFS Server has the IP address 192.168.1.10, log in to the Abiquo Remote Services host.
Check that the NFS share you specified during the Remote Services install is in the /etc/fstab file:
[root@abiquo-rs ~]# cat /etc/fstab /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 192.168.1.10:/opt/vm_repository /opt/vm_repository nfs defaults 0 0
And check that it is mounted at /opt/vm_repository
[root@abiquo-rs ~]# mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda1 on /boot type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) 192.168.1.10:/opt/vm_repository on /opt/vm_repository type nfs (rw,addr=10.60.1.72)
Do the same thing on the Abiquo V2V Services host.
Check the .abiquo_repository file is present on the NFS share
On the Remote Services host, check that the NFS share is mounted.
[root@abiquo-rs ~]# cd /opt/vm_repository/ [root@abiquo-rs ~]# ls .abiquo_repository
If the .abiquo_repository file is not present, then create it:
touch /opt/vm_repository/.abiquo_repository
Check the ownership of the NFS share
On the Remote Services host, check the owner of the NFS share mounted as /opt/vm_repository.
[root@abiquo-rs ~]# ls -ld /opt/vm_repository/ drwxr-xr-x 13 root root 1714 abr 17 13:51 /opt/vm_repository/
If this /opt/vm_repository folder is not owned by tomcat, then change the owner:
[root@abiquo-rs ~]# chown -R tomcat:tomcat /opt/vm_repository
Now the tomcat user will have full access to this folder.
[root@abiquo-rs ~]# ls -ld /opt/vm_repository/ drwxr-xr-x 1 tomcat tomcat 1714 abr 17 13:51 /opt/vm_repository/
Change the NFS folder
See How to migrate the NFS repository to a new NFS destination