Unable to Run Caspida Cleanup - Kafka Broker Not Reachable

Available Languages

Updated:September 29, 2026
Document ID:SPLK047946

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

UBA 5.3.0

Description

 While configuring warm standby, issues with the Kafka broker and Zookeeper were reported, preventing the Caspida cleanup process from running successfully.


Investigation

Upon reviewing the health check, it was found that some of the expected services were not running in the UBA environment.



To address the issue, the UBA components were started instead of all Caspida services using the following command:

/opt/caspida/bin/Caspida start-all --no-caspida

The Caspida cleanup process was then attempted again using the command:

/opt/caspida/bin/CaspidaCleanup

However, a Kafka broker issue (not reachable) was encountered.

After checking the Kafka server status with the command: 

sudo service kafka-server status

 It was found that the Kafka server was not running.


Resolution

The Kafka server was started manually with the following command:

sudo service kafka-server start

Once the Kafka server was running, the Caspida cleanup process was successfully completed.

 

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco