| Table of Contents |
|---|
| Info |
|---|
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 configuration file has the correct settings for your NFS share.
Assuming your NFS Server server has the IP address 192.168.1.10. The entries for nfs NFS in file the /opt/abiquo/config/abiquo.properties file should look like the example below.
| Code Block |
|---|
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, after you have finished making changes to the NFS folder, restart the Abiquo Tomcat server
...
Check the NFS repository is mounted
Now that After you install the Abiquo Platform has been installed, we need to make sure platform, check 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 .
Check that the NFS share you specified during the Remote Services install is mounted at /opt/vm_repository and the proper config has been added to in the /etc/fstab file:
| Code Block |
|---|
[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
| Code Block |
|---|
[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.
...
On the Remote Services host, check that the NFS share is mounted.
| Code Block |
|---|
[root@abiquo-rs ~]# cd /opt/vm_repository/ [root@abiquo-rs ~]# ls .abiquo_repository |
If the .abiquo_repository file is not present, then create it:
| Code Block |
|---|
touch /opt/vm_repository/.abiquo_repository |
After you have finished making all your changes to the NFS folder, restart the Tomcat server.
...
Check the ownership of the NFS share
On the Remote Services host, check the owner of the NFS share mounted as /opt/vm_repository.
| Code Block |
|---|
[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:
| Code Block |
|---|
[root@abiquo-rs ~]# chown -R tomcat:tomcat /opt/vm_repository
|
Now the tomcat user will have full access to this folder.
| Code Block |
|---|
[root@abiquo-rs ~]# ls -ld /opt/vm_repository/
drwxr-xr-x 1 tomcat tomcat 1714 abr 17 13:51 /opt/vm_repository/
|
After you have finished making all your changes to the NFS folder, restart the Tomcat server.
...
Change the NFS folder
See How to migrate the NFS repository to a new NFS destination
...
How Abiquo mounts the NFS repository on vCenter hosts
You configure the NFS repository with the abiquo.appliancemanager.repositoryLocation property. When you create a datacenter, Abiquo will store the repository location in the Abiquo database.
In general, Abiquo will mount the NFS repository automatically. But the platform will not check that the repository is correctly mounted on hosts in the vCenter cluster until it needs to use the repository.
When a user tries to deploy a VM, the platform will select a host and check that it can mount the datastore and the NFS repository. If the platform cannot correctly mount the NFS repository on any of the hosts in the cluster, the deploy will fail.
If the NFS repository is correctly mounted, the platform will copy the disk from the repository to the datastore. If the selected host is not connected or in maintenance mode, the platform may deploy the VM to another host.
...
Troubleshooting NFS repository mount on vCenter hosts
Abiquo only checks the mount information for hosts in the cluster that are connected and not in maintenance mode.
If it is not possible to mount the NFS on a host, then Abiquo doesn't abort the operation. It will report errors as a WARN in the virtualfactory.log of the Virtualization Manager remote service. The message is: Cannot mount nas 'nfs-location' in 'hostName'
If a host in the cluster mounts the NFS repository but it is not properly mounted, then the platform does not try to fix it. It will report this error as a WARN in virtualfactory.log of the Virtualization Manager remote service. The message is: NFS repo 'nfs-location' in host 'hostName' ('host-id') - not mounted, not accessible or not readWrite