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. The flexsnap-listener pod is unable to communicate with RabbitMQ
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

The flexsnap-listener pod is unable to communicate with RabbitMQ

After successfully deploying Cloud Scale, if the RabbitMQ server is deleted, it gets recreated with a new server IP.

However, the flexsnap-nginx server configuration does not get updated to reflect the new RabbitMQ server IP. Hence, the flexsnap-listener pod is unable to communicate with RabbitMQ through flexsnap-nginx server.

Workaround:

To resolve the issue, perform the following:

  • After RabbitMQ is recreated, restart the flexsnap-nginx server to update its configuration.

  • Restart flexsnap-listener server to get the listener pod in running state.

Feedback

Was this page helpful?
Previous

Issues with logging feature for Cloud Scale

Next

Job remains in queue for long time

Feedback

Was this page helpful?