Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

This section contains basic NFS server troubleshooting.

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, restart the Abiquo Tomcat server



Check the NFS repository is mounted

Now that the Abiquo Platform has been installed, we need to make sure that the NFS Repository used to store the VM Templates and VM disk conversions 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 and make sure the NFS share you specified during the Remote Services install is mounted at /opt/vm_repository and the proper config has been added to 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

[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.

If the .abiquo_repository file is not present, then create it:

touch /opt/vm_repository/.abiquo_repository



  • No labels