Issue
- I can’t collect a support bundle because I can’t login, or Jenkins is not able to start
Environment
- CloudBees Core
- CloudBees Core on modern cloud platforms - Managed Master
- CloudBees Core on modern cloud platforms - Operations Center
- CloudBees Core on traditional platforms - Client Master
- CloudBees Core on traditional platforms - Operations Center
- CloudBees Jenkins Enterprise
- CloudBees Jenkins Enterprise - Managed Master
- CloudBees Jenkins Enterprise - Operations Center
- CloudBees Jenkins Platform - Client Master
- CloudBees Jenkins Platform - Operations Center
- CloudBees Jenkins Distribution
- Jenkins LTS
Resolution
When the Support Core plugin is installed, it automatically stores a bundle every hour in $JENKINS_HOME/support. These bundles are purged using an exponential retention strategy so that they do not overflow disk space.
You can find these support bundles in $JENKINS_HOME/support/ named either support_YYYY-MM-DD_hh.mm.ss.zip or cloudbees-support_YYYY-MM-DD_hh.mm.ss.zip where YYYY-MM-DD andhh.mm.ss are the UTC date and time respectively when the bundle was generated.
The latest support bundle (and sometimes an older bundle before the issue occurred) can be helpful for CloudBees Support to diagnose your issue.
You can inspect the contents of these file(s) to assure yourself that they do not contain information you do not want to share with CloudBees. You can even unpack and repack bundle(s) if there is some specific piece of information that you need to remove from some bundle(s).
0 Comments