This document provides a list of quick answers to issues caused by incorrect configuration.
Events problems
Only events related to roles are displayed
Symptoms
No events except those related to roles are displayed.
Solution
Verify that you correctly configured the network when you installed Abiquo. If you configured one of the NICs using DHCP, it has to deliver a hostname and gateway address. To verify this is properly configured, access the /etc/hosts file and check if your hostname appears in it; if not, add it.
Infrastructure problems
Remote services error despite green lights on checks
Symptoms
When creating a new physical data center, Abiquo gives an error that some of the remote services aren't properly configured although every check is green.
Solution
- Review the NFS configuration in the file /opt/abiquo/config/abiquo.properties.
- Restart the Tomcat server "service abiquo-tomcat restart".
- Check there is a file in the directory /opt/vm_repository/ named ".abiquo_repository".
Catalogue problems
Downloaded VM templates do not appear in the catalogue
Symptoms
- The server has been installed or restarted recently.
- Images appear as downloaded in the remote repository.
- No images appear in the appliance library.
Solution
Check that the NFS repository is correctly configured.
Appliance manager problems
Appliance manager is not working
Symptoms
- Appliance manager is not working
- NFS server is located on the same machine as the remote services.
- Error message: "Can't validate ''abiquo.appliancemanager.repositoryLocation'' 127.0.0.1:/opt/vm_repository. It's a local repository"
Solution
Disable the check for mounted repositories by setting the property "abiquo.appliancemanager.checkMountedRepository" to false on /opt/abiquo/config/abiquo.properties. By default this property is set to true.
Virtual datacenter problems
Not enough resources available
Symptoms
When deploying, you receive the notification: "Not enough resources available".
Solution
The problem is there are not physical machines with enough resources (HD, CPU, RAM) to deploy the virtual machine.
There are 2 possible solutions:
- Undeploy some virtual machines
- Make sure you have a physical machine with enough resources to be able to deploy
Hyper-V
Hyper-V does not deploy images
Symptoms
An error occurred when calling the deploy operation in a Hyper-V machine. This error appears in the log:
13:02:15.374 INFO c.a.v.machine.impl.AbsHyperVMachine - Cloning the virtual disk from: \\10.60.1.72\opt\vm_repository\1\rs.bcn.abiquo.com\centos_vhd\cent
os.vhd to C:\\ABQ_50a782d5-e535-425d-a552-545eb699d849.vhd
13:02:15.601 ERROR c.a.v.utils.hyperv.HyperVUtils - Monitoring job result error:
ErrorCode: 32768 ErrorDescription: 'The system failed to convert '\\10.60.1.72\opt\vm_repository\1\rs.bcn.abiquo.com\centos_vhd\centos.vhd'. Error
Code: The network name cannot be found.
13:02:15.614 ERROR c.a.v.machine.impl.AbsHyperVMachine - Failed to deploy machine :
org.jinterop.dcom.common.JIException: An error was occurred when calling an operation in a Hyper-V machine
Solution
Although the URI is correct, Hyper-V accesses the filesystem using Samba. In Samba, the directory is aliased as vm_repository. To change this directory go to the server, /opt/abiquo/config (remember that this path could be in a chroot system). Then edit the abiquo.properties file and enter the following property containing the IP address of the CIFS server:
abiquo.virtualfactory.hyperv.repositoryLocation = //<SERVER_IP>/vm_repository/
and restart the Tomcat server.
Hyper-V does not create an instance
Symptoms
- Only happens in Hyper-V
- This error appears in Events:
- Error bundling VirtualAppliance: number
- An error occurred when calling an operation in a Hyper-V machine
- This error appears in the log:
ErrorCode: 32769 ErrorDescription: 'The system failed to convert 'C:\\localRepository\\e13fcbec-2475-46c1-9f90-66aa1f2850be.vhd'. Error Code: General access denied error14:54:17.420 ERROR c.a.v.v.i.VirtualapplianceresourceDeployer - An error occurred: org.jinterop.dcom.common.JIException: An error was occurred when calling an operation in a Hyper-V machineErrorCode: 32769. ErrorDescription: 'The system failed to convert 'C:\\localRepository\\e13fcbec-2475-46c1-9f90-66aa1f2850be.vhd'. Error Code: General access denied error
Solution
Check the smb.conf file is correctly configured. This file is configured during installation. For more information, see VM repository folder.