When starting mongo ops manager and checking mongodb process it shows 0 mongods, and in system warnings throws the warning "Unable to find process for member XXX:27020 in rs_1"

I can conect from all the servers to all the replica sets, and from the server where the mongo ops manager process runs I also can conect to all the replica sets.


  • Hi, Please add mongoDB version and rs.status() from primary – Priyanka Kariya Feb 11 at 11:13
  • mongo db.version() >> 4.0.1 – Willy Castillo Feb 12 at 16:59

Ops Manager uses lower letter hostnames for the monitoring, so after changing the replicasets configurations to lowercase everything works fine

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.