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.

Resolution
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]