Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  3. Section IV. Maintenance
  4. Troubleshooting
  5. Troubleshooting AKS and EKS issues
  6. Post Kubernetes cluster restart, flexsnap-listener pod went into CrashLoopBackoff state or pods were unable to connect to flexsnap-rabbitmq
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Post Kubernetes cluster restart, flexsnap-listener pod went into CrashLoopBackoff state or pods were unable to connect to flexsnap-rabbitmq

After Kubernetes cluster restart, flexsnap-listener pod went into CrashLoopBackoff state or pods such as flexsnap-coordinator, flexsnap-agent and so on were unable to connect to flexsnap-rabbitmq.

This issue can be resolved by restarting the NetBackup Snapshot Manager services in the following order using the kubectl delete <pod-name> -n <namespace> command:

flexsnap-certauth

flexsnap-rabbitmq

flexsnap-postgres

flexsnap-listener and so on.

Feedback

Was this page helpful?
Previous

Failed to register Snapshot Manager with NetBackup

Next

Post Kubernetes cluster restart, issues observed in case of containerized Postgres deployment

Feedback

Was this page helpful?