Problem with MMS configuration

[Enrique Albes]

Hello,

I'm trying to configure MongoDB Management Service (MMS) in order to monitor a test sharded cluster but I'm having trouble with it. I've created an account in the web page and successfully installed the MMS agent (in the Administration/Agents tab I can see the agent is communicating with MMS properly). The cluster is formed by two shards (S0, S1) each being a replica set with three members (two data nodes and an arbiter), three config servers and one mongos (all of them running in Windows 200x Server machines). The processes distribution is the following:

MACHINE PROCCESS

-----------------------------------------

1 mongos, MMS agent

2 S0-RS0, C0

3 S0-RS1, S1-RS2 (Arbiter), C2

4 S1-RS0, C3

5 S1-RS1, S0-RS2 (Arbiter)

Where SX-RSY stands for Shard X - Replica set member Y and C means config server .

When I try to configure the hosts related to the cluster through the "Deployment/+Add/Create new cluster" option, I get the following error message:

"Error: Unable to find enough servers. Please check the server eligibility settings and port ranges, and ensure all agents are running"

To tell the truth, I do not completely understand what values are expected in the "Create new cluster" form fields. For instance:

- Name: Does it have to match some specific string or it is just a name for the MMS interface?

- Eligible Server RegExp: This is very confusing for me. I'm using several machines for the cluster with arbitrary Windows names and I do not know what is expected here. I've tried using a static ip

address shared by all of them and the '.' character but I do not know what is really expected.

- Eligible Port Range: Does this refer to a range that contains all the ports involved in the cluster (mongos, config servers, data nodes...)? The range could be very big compared with the                           number of effective ports being used...

- Config Server Configuration (Distribution): How can I indicate the three ports of the config servers? Is it enough with one?

- Shard Name Prefix: Here I have the same question as with the name field...

- DB Path Prefix: I do not know what prefix refers as each process has its own --dbpath value...

I assume that only the agent should be able to connect to the cluster processes (what I already checked).

Could anyone help me with this please?

Thank you very much in advance

[Asya Kamsky]

Are these existing nodes with an already running cluster?

You can only provision a new cluster using MMS and then monitor it.
You cannot initiate monitoring of a cluster that already exists...

Asya

> --
> You received this message because you are subscribed to the Google Groups
> "mongodb-user"
> group.
>
> For other MongoDB technical support options, see:
> http://www.mongodb.org/about/support/.
> ---
> You received this message because you are subscribed to the Google Groups
> "mongodb-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mongodb-user...@googlegroups.com.
> To post to this group, send email to mongod...@googlegroups.com.
> Visit this group at http://groups.google.com/group/mongodb-user.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mongodb-user/cf56cdd0-4bba-448b-8b37-accba80a39a4%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Enrique Albes]

Yes, they are... 

I tried MMS several months ago with a standalone instance running on a Linux machine (Ubuntu) and I have noticed MMS interface has changed since then. I would swear that at that time my instance was already running when I created the account on MMS then I downloaded the agent during the the registration process and finally there was an option to add hosts.

Now I see that the MMS setup process includes a step in order to install an automation agent. The problem I have with this step is that when I try to download this agent I see that there is no version for Windows operating systems (there are versions for Ubuntu, Other Linux, RHEL/CenOS/SUSE Amazon Linux and Mac OS X). For this reason I had to stop at this point the MMS setup normal process and downloaded directly the Windows monitoring agent hoping that after that, I would be able to add my cluster hosts. Then I noticed that in MMS web interface there was not the Hosts menu anymore, but two menus related with machines (Deployment and Servers). In Servers menu I see that when I press "+Add" I need AWS (which I am not using, I just have local machines), so I tried the Deployment menu, but according to your response this is related to provision the cluster from MMS interface instead of adding it later... Up to now I assume that is not possible to complete the process for Windows environments.

While writing this, paying more attention to the MMS home page, I have seen a link called "Looking for MMS Monitoring or Backup?" so now I understand that this service has changed...

Thank you

[Stephen Steneker]

On Thursday, 23 October 2014 19:06:20 UTC+11, Enrique Albes wrote:

I tried MMS several months ago with a standalone instance running on a Linux machine (Ubuntu) and I have noticed MMS interface has changed since then. I would swear that at that time my instance was already running when I created the account on MMS then I downloaded the agent during the the registration process and finally there was an option to add hosts.

Hi Enrique,

As you noted the MMS product has changed and now integrates automated provisioning/deployment for new groups:

 http://blog.mongodb.org/post/99991498968/mongodb-management-service-re-imagined-the-easiest-way

However, you mentioned creating an MMS group a few months ago -- you should still be able to add new hosts into your existing group. The "classic" groups do not have automation support and the process should be similar to what you did previously (install a monitoring agent and add hosts).

 

Now I see that the MMS setup process includes a step in order to install an automation agent. The problem I have with this step is that when I try to download this agent I see that there is no version for Windows operating systems (there are versions for Ubuntu, Other Linux, RHEL/CenOS/SUSE Amazon Linux and Mac OS X).

That is correct .. there is no automation agent for Windows yet.

 

For this reason I had to stop at this point the MMS setup normal process and downloaded directly the Windows monitoring agent hoping that after that, I would be able to add my cluster hosts. Then I noticed that in MMS web interface there was not the Hosts menu anymore, but two menus related with machines (Deployment and Servers). In Servers menu I see that when I press "+Add" I need AWS (which I am not using, I just have local machines), so I tried the Deployment menu, but according to your response this is related to provision the cluster from MMS interface instead of adding it later... Up to now I assume that is not possible to complete the process for Windows environments.

Environments do not have to be provisioned via AWS as long as you are able to install automation agents for MongoDB deployment. That does preclude Windows environments at the moment, though.

Regards,

Stephen