IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

Cb Response: How to Diagnose a Red Toaster Error

Cb Response: How to Diagnose a Red Toaster Error

Environment

  • Cb Response: All versions

Objective

How to diagnose a red toaster error within the Cb Response UI that says, "An unexpected error has occurred".  This may occur when navigating from page to page within the UI.

red-toaster.png

Resolution

  • Which page is the error occurring on?  Provide the URL.

  • When did it start and what changed?
  • Which browser and browser version is being used?
  • Restart services as a preliminary first step from the master server.

1. Stop the services (Single Server).

#: service cb-enterprise stop

a. If using a cluster:

#: /usr/share/cb/cbcluster stop

2. Find running Cb processes.

#: ps -ef | grep cb (perform on all nodes if using a Cluster)

3. Kill the running processes according to Process ID.

#: kill -9 <all remaining Cb PIDs> (perform on all nodes if using a Cluster)

4. Start the services (Single Server).

#: service cb-enterprise start

a. If using a cluster:

#: /usr/share/cb/cbcluster start

  • Check for an expired license by running the command below.  If using a Cluster do this on all nodes.

#: /usr/share/cb/cblicense -d

  • Reproduce the issue while providing a HAR file from Chrome:

Cb Response: How To Generate A Har File and Console Logs In Chrome

  • Provide CbDiags to the Support department to troubleshoot the issue further.

Collecting logs for Troubleshooting [Server - Cb Response]

Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎06-04-2018
Views:
1066
Contributors