Troubleshooting issues with the Chef integration

This topic describes possible issues that may occur with the integration, and what actions to follow. The topic contains the following sections:

Review the pre-requisites

Before you start using the Chef integration, ensure that the following key prerequisites are met:

• Identify the OS and architecture of servers in your environment.
• Download the Ruby interpreter and its dependencies for your server OS and architecture.
• BMC recommends that you download Ruby from the OS media to avoid any installation issues and runtime version mismatches.

See Overview and requirements for the Chef integration for the complete list of requirements.

If you are unable to install Chef-solo using BMC Server Automation

Try installing Chef-solo on the target server manually so that errors are logged. Then, review the log files to identify the issue.

If you have issues with Cookbooks

If you encounter issues with the cookbook, ensure the following:

• Validate the cookbook, if you downloaded it from the Chef Supermarket or any other source.
• Ensure that the cookbook is correctly defined.

For more information about how cookbooks are used in Chef-solo, see the Chef online technical documentation .

If the Chef Cookbook Job Fails

if you encounter issues with the cookbook job, perform the following steps:

1. Rerun the job using the Preserve Staging Area option.
2. Navigate to the /var/tmp/stage/chef directory on the target server where the job has failed.
3. Run the following command on the target:
   Chef –solo –c solo.rb–j node.json
4. Review the logs that are presented on the screen.

For more information about running Chef-solo from the command line, see the Chef online technical documentation.