CloudBees Jenkins Advisor Troubleshooting Guide

Issue

  • I’m not receiving any report emails after setting up CloudBees Jenkins Advisor plugin.

Environment

  • CloudBees Jenkins Enterprise (CJE)
  • Jenkins
  • CloudBees Jenkins Advisor Plugin
  • Support Core Plugin

Resolution

It’s worth noting that the CloudBees Jenkins Advisor service will only report new issues found, so if you did receive
an original email report after configuring the plugin, but haven’t received one since, then this might not be an issue.

General Knowledge

Error messages from the CloudBees Jenkins Advisor plugin for failed uploads start with:

SEVERE: Issue while uploading file to bundle upload service

Potential Issues

Support bundle too large

Upload will fail if the max file upload size is exceeded. The size is 200mb. If you are generating support bundles larger
than this then you will see the following in the logs:

SEVERE: Bundle upload failed. Response code was: 413. Response status text: Request Entity Too Large. Response body: {"message":"Maximum upload size of 2048 bytes exceeded; nested exception is org.apache.commons.fileupload.FileUploadBase$SizeLimitExceededException: the request was rejected because its size (230686720) exceeds the configured maximum (209715200)"}

Authentication Failed

Upload will fail if credentials are incorrect.

SEVERE: Issue while uploading file to bundle upload service: com.cloudbees.jenkins.plugins.advisor.client.InsightsClient$InsightsAuthenticationException: Authentication failed. Unable to get bearer token

You can use the “Test Connection” button in the CloudBees Jenkins Advisor plugin configuration page to verify whether the
configured credentials are correct.

Connection Refused

If your instance does not have public internet access then you will not be able to access the CloudBees Jenkins Advisor service.

SEVERE: Issue while uploading file to bundle upload service: com.cloudbees.jenkins.plugins.advisor.client.InsightsClient$InsightsAuthenticationException: Unable to authenticate. Reason: Connection refused

CloudBees Jenkins Advisor service uses the Jenkins proxy configuration. If your instance is behind a proxy then see - JenkinsBehindProxy

Server Too Busy

Might be reported as:

INFO: Bundle Upload thread is still running. Execution aborted.

Or, you might see a message containing http response code 429 - Too Many Requests - https://tools.ietf.org/html/rfc6585#section-4

Unexpected / Other Issues

Probably indicate a bug in the plugin or the service. Usually should receive http response code 500 - Internal Server Error - http://tools.ietf.org/html/rfc7231#section-6.6.1

Reporting Issues

See How to report an issue.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.