Troubleshooting (Plugins and Integrations)

EOL and Deprecation list:

• Jenkins Plugin versions < 2.0 EOL
• Anka GitLab Runner versions < 1.0 EOL
• Anka GitLab Runner at any version is now Deprecated. Please use the Custom Executor.

Please perform the checklist steps below before reaching out to customer support.

Troubleshooting Checklists

These checklists give you an idea where to look and what logs to check for indications of exactly what’s wrong when you see failures.

Anka Cloud Gitlab Executor

1. Find the job’s log inside of your Gitlab and gather the VM and node information from it, as well as the failure messages.
2. If you have access to the gitlab runner logs, collect those for the time period of the failure. Logs in the runner are labelled with job=#, matching the job ID.
3. Collect the logs in the Anka Build Cloud Controller from the time period of the failure (Controller > Logs > Service: Controller)
4. Perform the Anka Virtualization checklist and check the logs at the time of the error on the Anka Node that ran the VM.

Gitlab Runner (deprecated)

Our gitlab runner is based on the core and official gitlab runner release, so the official troubleshooting guide is also good to review.

1. Find the job’s console log inside of your Gitlab instance and gather the VM and node information from it.
2. If you have access to the gitlab-runner logs, collect those for the time period of the failure. Logs in the runner are labelled with job=#, matching the job ID.
3. Collect the logs in the Anka Build Cloud Controller from the time period of the failure (Controller > Logs > Service: Controller)
4. Perform the Anka Virtualization checklist and check the logs at the time of the error on the Anka Node that ran the VM.

Jenkins

1. When you first kick off a job in Jenkins, you can find the “node” or “computer” Jenkins ties the VM our plugin spins up to at the top of the Console Output. If you go to the node’s page, you’ll be able to access the “Logs” which show you Jenkins connecting to the Anka VM and any potential failures there. This is useful to check first, but the log is only available until the VM is terminated and Jenkins deletes the node.
2. Gain a understanding of what specifically is failing from the Console Output in the Jenkins job.
3. Collect the logs for the Anka Build Cloud Controller from the time period of the failure (Controller > Logs > Service: Controller).
4. Find the Jenkins System Log and look at the time of the failure for any errors related to the Anka plugin or Jenkins in general.
5. Perform the Anka Virtualization checklist and check the logs at the time of the error on the Anka Node that ran the VM.

Buildkite

1. Gain an understanding of what specifically is failing from the specific build log at buildkite.com.
2. Ensure the buildkite agent is configured correctly, registered and showing up properly on your buildkite organization agents page, and has an active status.
3. Perform the Anka Virtualization checklist and check the logs at the time of the error on the Anka Node that ran the VM.

Github Actions

1. Gain an understanding of what specifically is failing from the actions run log.
2. Follow official troubleshooting guide from Github.
3. Perform the Anka Virtualization checklist and check the logs at the time of the error on the Anka Node that ran the VM.

Azure Devops Pipelines

1. Gain an understanding of what specifically is failing from the pipeline logs.
2. Follow official troubleshooting guide from Microsoft.
3. Perform the Anka Virtualization checklist and check the logs at the time of the error on the Anka Node that ran the VM.

Anka Packer Plugin

1. Run your packer build with debug logging enabled: export ANKA_LOG_LEVEL=debug; export ANKA_DELETE_LOGS=0; PACKER_LOG=1 packer build. . .
2. Looks at the various anka commands in the logs to determine the exact one failing (if an anka command at all).

Teamcity

1. Check the teamcity server logs for errors.
2. Check the /Users/anka/buildAgent/logs/teamcity-agent.log inside of the VM where you’ve installed the build agent and look for errors.
3. Ensure your Controller URL and also the Server URL (under the cloud profile) are correct and accessible to the VM’s network.
4. Double check that the Agent Path is set to the root of the agent you installed in the VM. It cannot be a sub folder like bin, etc.
5. Ensure your Teamcity Agent was installed properly. You can find our installation instructions here.

Troubleshooting Guides