Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.

Abiquo 2.6

Skip to end of metadata
Go to start of metadata

This guide will explain how to troubleshoot Chef Enabled VMs. Everything explained here is related to the VM itself, after deployment has occurred. If you want to troubleshoot Abiquo Chef integration (error messages in the GUI, enabling Chef integration in Abiquo, etc), please refer to the guide Troubleshooting Abiquo Chef Integration. Abiquo supplies official Abiquo/Opscode Chef enabled VM templates. Templates customized by the end user are not currently supported.

Collecting the necessary information to troubleshoot your installation

Chef enabled VMs have two important software pieces installed:

1. Opscode Chef Client
2. Abiquo Chef Agent

The Abiquo Chef agent is started when the VM boots and is responsible for launching the Opscode Chef Client after gathering the required information from the Abiquo platform (via Abiquo API).

Log files

There are two log files where info and error messages are reported by those two clients:


This log file stores information related to the Abiquo Chef agent run. Any problem related to the Abiquo Chef agent will be logged here.


This log file stores the Chef client log. Any problem related to the Chef client run (when downloading or applying recipes) will be logged here.

The Abiquo support staff will request these log files when required.

Configuration Files

Chef client configuration

Everything required by the Opscode chef client to run is stored in '/etc/chef'. If the directory is empty or does not exist, the problem is usually related to the Abiquo Chef agent.

DHCP client leases file

The Abiquo Chef agent uses the DHCP client lease file to get the necessary info to communicate with the Abiquo API. These files are usually located in the following directories (depending on the Linux distribution):


Network interface information

Abiquo Chef agent errors are usually related to networking issues (Network interface did not get DHCP configuration, Abiquo API server unreachable, etc).

Abiquo Support staff will request the output of the following command (from within the VM) when required:

ifconfig -a

Sample ouput:

eth0      Link encap:Ethernet  HWaddr 00:13:93:C1:81:C8  
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::216:d3ff:fec6:81d8/64 Scope:Link
          RX packets:36291744 errors:0 dropped:501 overruns:0 frame:0
          TX packets:24082889 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:46651233047 (43.4 GiB)  TX bytes:9767920879 (9.0 GiB)
          Interrupt:20 Memory:f8200000-f8220000 

lo        Link encap:Local Loopback  
          inet addr:  Mask:
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:77509 errors:0 dropped:0 overruns:0 frame:0
          TX packets:77509 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:10750209 (10.2 MiB)  TX bytes:10750209 (10.2 MiB)

What kind of problems can occur when deploying Chef Enabled VMs?

Networking issues
No IP Address/DHCP Leases

If the chef-client does not receive a correct network configuration, it will not be able to contact the DCHP Server and receive the leases file that contains the Chef runlist. If this happens, Abiquo recommends that you undeploy the virtual machine, fix the network configuration and then deploy the virtual machine again.

Chef Client Issues
First Run Fails

If a problem occurs when you first run the chef-client, the chef client will not be registered on the Chef Server. There will be a message like the following in the chef log file.

I, [2012-02-27T14:06:07.433431 #1104]  INFO -- : chef-client -N
ABQ-9fb4f9a5-3e3b-49cb-a590-c95c69b792be --once -j /etc/chef/first-boot.json
-L /var/log/chef-client.log
E, [2012-02-27T14:06:09.588769 #1104] ERROR -- : chef-client run failed

The validation key is deleted for security reasons after the first run, whether it is successful or not. Abiquo recommends that you undeploy the virtual machine, check the configuration, and then redeploy.

  • No labels