Mongodb-mms Installation

MMS is MONGO cluster monitoring software.

MMS eats memory very much, when the virtual machine tests, 3G memory starts successfully, then fails on reboot, it is recommended not less than 4G memory.

MMS:

https://downloads.mongodb.com/on-prem-mms/rpm/mongodb-mms-3.6.2.596-1.x86_64.rpm

MMS Installation and configuration:

sudo yum localinstall mongodb-mms-3.6.2.596-1.x86_64.rpm

Modify the/mms/conf/conf-mms.properties file,

Vi/opt/mongodb/mms/conf/conf-mms.properties

The following parameters must be set:

# # MMS monitoring service, full URL mms.centralurl=http://test:8080

# # User name and port for MMS backup service mms.backupcentralurl=http://test:8081

# #Send a general email Mms.fromemailaddr=

# # Send a reply to a general email mms.replytoemailaddr=

# # Send Message from MMS admin mms.adminfromemailaddr=

# # Send message or reply to MMS Administrator mms.adminemailaddr=

# # Send a bounce message mms.bounceemailaddr=

# # MMS connects to the MongoDB server's connection string, which is the MMS application database Mongo.mongouri

# # If Mongo.mongouri is using a replica set, you need to specify the name of the replica set Mongo.replicaset

mms.centralUrl=http://centosvm2:8080
mms.backupCentralUrl=http://centosvm2:8081
mms.fromEmailAddr=liugh7@lenovo.com
mms.replyToEmailAddr=liugh7@lenovo.com
mms.adminFromEmailAddr=liugh7@lenovo.com
mms.adminEmailAddr=liugh7@lenovo.com
mms.bounceEmailAddr=liugh7@lenovo.com
mongo.replicaSet=mmsreplset

Centralurl will be used in Automationagent installation monitoringagent, if the mismatch is difficult to find this error, to be paired with each physical machine can access the URL address, be sure to pay attention!

mongo.mongouri=mongodb://127.0.0.1:17017,127.0.0.1:17018

Start the MMS service

Mongodb-mms start

Note: When you start MMS, you do a pre-flight check

Visit http://127.0.0.1:8080, will be transferred to the following page, you need to register an account

Registered

Registration success after the automatic login, to the configuration page, asterisking must fill, I only fill in the "*" number, as follows: Mainly mailbox, other by default

Then always point to the next step until the admin interface

Deployment

We can create a new MongoDB deployment

Create a remote deployment

And then

These three options are, in turn, stand-alone instances, replica sets, shard clusters

Select a third shard cluster

Fill in: Cluster name, number of shards, number of nodes, shard prefix, storage path

Next, let's choose the number of servers,

Then install the agent, select the type of server

Will eject the installation information, follow the prompts to install it can

To install the agent's command line log:

[luxuelin@centosvm ~]$ curl -OL http://0.0.0.0:8080/download/agent/automation/mongodb-mms-automation-agent-manager-4.5.10.2429-1.x86_64.rhel7.rpm
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 7810k 0 7810k 0 0 17.3M 0 --:--:-- --:--:-- --:--:-- 17.3M
[luxuelin@centosvm ~]$ sudo rpm -U mongodb-mms-automation-agent-manager-4.5.10.2429-1.x86_64.rhel7.rpm
[sudo] luxuelin's password:
Sorry, please try again.
[sudo] luxuelin's password:

is the display after clicking GenerateKey:

Note that saving Mmsapikey is hard to find after you turn off the page.

[luxuelin@centosvm ~]$ sudo vi /etc/mongodb-mms/automation-agent.config
[sudo] luxuelin's password:
[luxuelin@centosvm ~]$ sudo systemctl start mongodb-mms-automation-agent.service
[luxuelin@centosvm ~]$

In the second step, generate the secret key, need to fill in the password, and then automatically fill in the following file, we can copy and paste

(Here is the management key of the connection, we click in can delete, after the agent will lose access to the MongoDB cloud ability)

Click Verify to complete the deployment (if the key changes to "try again", the validation fails and you look back to see which steps are not done).

You can also import an existing database

Results after installing the agent ibid.

Then automatically install the Monitoring agent and backup agent

This is the result of the test on my Machine (Rushering), the configured IP is 192.168.126.131,port is 17017 (MONGOs service port)

But the agent I installed was installed on the 192.168.126.130, stating that the agent and the monitored MONGO can be cross-machine:

Next configure the complete cluster monitoring, each machine needs to install and configure the agent:

mmsbaseurl=http://192.168.126.132:8080

Note that the Mmsbaseurl in the/etc/mongodb-mms/automation-agent.config file of other machines should be changed to a central IP instead of a 0.0.0.0

The following are the execution log instances on the other two virtual machines:

[luxuelin@centosvm ~]$ curl -OL http://192.168.126.132:8080/download/agent/automation/mongodb-mms-automation-agent-manager-4.5.10.2429-1.x86_64.rhel7.rpm % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 7810k 0 7810k 0 0 23.4M 0 --:--:-- --:--:-- --:--:-- 23.5M [luxuelin@centosvm ~]$ sudo rpm -U mongodb-mms-automation-agent-manager-4.5.10.2429-1.x86_64.rhel7.rpm [sudo] luxuelin's password: [luxuelin@centosvm ~]$ sudo vi /etc/mongodb-mms/automation-agent.config [luxuelin@centosvm ~]$ sudo vi /etc/mongodb-mms/automation-agent.config [luxuelin@centosvm ~]$ sudo systemctl start mongodb-mms-automation-agent.service [luxuelin@centosvm ~]$

View

New No data

Configure Local mode for OPS manager Servers without Internet Access (Optional) Set Ops Manager to Local mode. Click Admin in the upper right corner to open system administration. From the General tab, click Ops Manager Config. Click the Miscellaneous button at the top of the page. For Version Manifest Source, select Local. Note the directory specified in Versions directory. This is the directory on your Ops Manager servers where you'll store the MongoDB binaries. For Backup Version Auto Download, select False.

Start the automationagent on each machine:

[luxuelin@centosvm0 router]$ sudo systemctl start mongodb-mms-automation-agent.service
[sudo] luxuelin's password:
[luxuelin@centosvm0 router]$

[luxuelin@centosvm1 router]$ sudo systemctl start mongodb-mms-automation-agent.service
[sudo] luxuelin's password:
[luxuelin@centosvm1 router]$

Check the MMS backstage to see if the three agents are connected:

Indicates that the agent configuration is all right.

Mongodb-mms Installation