Skip to main content
Question

MongoDB stuck in Not Ready state

  • April 9, 2025
  • 1 reply
  • 67 views

Forum|alt.badge.img+1

 

Our MongoDB is healthy and actively running, but its stuck in Not Ready state. We have two nodes mongodb - primary & secondary with Replica Set “rs0”
We also ensured that we used correct DB Username & Password

1 reply

sarvesh
Vaulter
Forum|alt.badge.img+3
  • Vaulter
  • July 9, 2025

Hi, apologies for the delayed response. This thread is a few months old — are you still experiencing the issue?

Since we don’t have access to the logs, we’re unable to confirm the exact cause. However, you can review the points below which might help in identifying or resolving the problem:

If the client name and the MongoDB host name are different, the mongodb host name must have an IP address resolvable by Commvault, and must be part of the bind_ip command line option on the MongoDB server.

refer documentation for more details: https://documentation.commvault.com/2024e/expert/configuring_mongodb_client.html
 
You can confirm the hostname from Mongo end via rs.config()

Do it for all the nodes.


Feel free to share more details if the issue persists — happy to assist further.