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 at
/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 catalogue.
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
of127.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 VM.
There are 2 possible solutions:
Undeploy some VMs
Make sure you have a physical machine with enough resources to be able to deploy
Oversubscribe your physical machines with an allocation rule for load level compute resources