couple of days ago mms stopped collecting data and showing that all hosts are down: https://mms.mongodb.com/
I thought it may be because agent is old, so installed 2.3.1 version on two hosts, but nothing changed so far
10gen, can you help on that?
tetlika wrote:
couple of days ago mms stopped collecting data and showing that all hosts are down: https://mms.mongodb.com/host/list/4e44f4be14587819403c 9268 I thought it may be because agent is old, so installed 2.3.1 version on two hosts, but nothing changed so far
Hi Tetlika,
The error in the MMS monitoring agent log indicates the agent is unable to connect to your hosts. In your MMS group you currently have eight agents running (check the Monitoring Agents list). Only one agent can be active at a time and the additional agents act as "standby".
The active agent at the moment has /dev/ in the hostname, so I suspect this agent is running in your dev environment and unable to connect to production hosts. There's also one very old agent in the mix (1.6.2).
I would recommend culling the list of agents to one with a standby, and make sure the agents are able to connect to your production environment. For more tips, please have a read of the MMS Monitoring Diagnostic and Troubleshooting Guide.
thanks Stephen
Hi Stephen. We have kind of similar problems: We changed our host, meaning we currently added a new one while the old is not functioning. But the monitoring and backup agents on the new host are standby. do you mean that we need to delete the old host from mms or it is enough to switch off agents (somehow)?
One more thing to add is that we would like the old host to stay since there are backups that we might need.
Here is link to our account https://mms.mongodb.
anybody? please help.
It looks like your new host has the same replica set name as your old host. MMS Backup uses replica set names as unique identifiers. Please change the name of your replica set if you want to keep your old backups.
댓글 없음:
댓글 쓰기