- Install Ops Manager >
- Advanced Configuration Options >
- Configure Local Mode for Ops Manager Servers without Internet Access >
- Resolve Pre-flight Check Failure
Resolve Pre-flight Check Failure¶
When you start Ops Manager in Local Mode, Ops Manager performs a
pre-flight check. This check verifies if you downloaded all the MongoDB
binary archives for at least one platform of the MongoDB versions you
selected in the Version Manager to the Versions
Directory
on the Ops Manager server. If these binaries were not
downloaded, Ops Manager fails this check and stops.
To pass the pre-flight check, you can either:
- Install all of the binaries for every version of MongoDB you need in the
Versions Directory
or - Reconfigure Ops Manager temporarily so it can start, then change the versions of MongoDB your Ops Manager server supports.
This tutorial outlines the steps to configure Ops Manager temporarily to resolve the pre-flight check failure and return to Local Mode setting.
Change Configuration File to Allow Ops Manager to Start¶
To reconfigure Ops Manager temporarily:
Open the Ops Manager configuration properties file.¶
On your Ops Manager server, open the Ops Manager configuration properties file. The configuration properties file is located in the following path:
Platform | Configuration File Path | Install Guide |
---|---|---|
RHEL | /opt/mongodb/mms/conf/conf-mms.properties |
RPM |
Ubuntu | /opt/mongodb/mms/conf/conf-mms.properties |
DEB |
Linux Archive | <userSelected>/conf/conf-mms.properties |
Linux archive |
Windows | C:\MMSData\Server\Config\conf-mms.properties |
Windows |
Update the configuration file to change the source for MongoDB binaries.¶
Add the following line to change the source for the MongoDB binaries to be via the internet.
Save and close the file.
Repeat for each Ops Manager server. (Optional)¶
If you run Ops Manager with high availability, you must repeat the previous step on each Ops Manager server.
Start the Ops Manager service on each Ops Manager server.¶
Platform | Configuration File Path |
---|---|
RHEL | sudo service mongodb-mms start |
Ubuntu | sudo service mongodb-mms start |
Linux Archive | <userSelected>/bin/mongodb-mms start |
Windows | sc start MMSDaemon |
If you run Ops Manager with high availability, you must repeat this step on each Ops Manager server.
Change the versions of MongoDB that Automation Agents can install.¶
- In Ops Manager, click Back To Group in the upper left to exit system administration.
- Click the Group link at the top of the page and select the desired group.
- Click Deployment, then the More drop-down list, then Version Manager.
- Select the checkboxes for the versions of MongoDB that you have made available on the Ops Manager Application host.
Important
For the selected versions, ensure that you have downloaded and
placed both the archived and extracted binaries in the
Versions Directory
. Otherwise,
Ops Manager fails a pre-flight check when starting in
Local Mode. See also
Start Ops Manager When All Versions Are Not Downloaded.
Important
You need to change the MongoDB version list for every group in Ops Manager.
Once you have changed which versions you want to support, continue to the Return to Local Mode procedure.
Return to Local Mode¶
Once you have resolved the pre-flight check errors, proceed with the following steps to run Ops Manager in Local Mode.
If these steps are not completed, Ops Manager remains in Internet mode and
displays a notice in the configuration page notifying you that the
Local Mode setting in your conf-mms.properties
overrides this setting.
To revert to Local Mode:
Open the Ops Manager configuration properties file.¶
On your Ops Manager server, open the Ops Manager configuration properties file. The configuration properties file is located in the following path:
Platform | Configuration File Path | Install Guide |
---|---|---|
RHEL | /opt/mongodb/mms/conf/conf-mms.properties |
RPM |
Ubuntu | /opt/mongodb/mms/conf/conf-mms.properties |
DEB |
Linux Archive | <userSelected>/conf/conf-mms.properties |
Linux archive |
Windows | C:\MMSData\Server\Config\conf-mms.properties |
Windows |
Delete the automation.versions.source
line.¶
Remove the following line to revert the change you made in the previous procedure and re-enables Local Mode.
Save and close the file
Repeat the previous steps on each Ops Manager server. (Optional)¶
If you run Ops Manager with high availability, you must repeat the previous steps on each Ops Manager server.
Restart the Ops Manager service on each Ops Manager server.¶
Platform | Configuration File Path |
RHEL | sudo service mongodb-mms restart |
Ubuntu | sudo service mongodb-mms restart |
Linux Archive | <userSelected>/bin/mongodb-mms restart |
Windows | sc stop MMSDaemon (with Administrator privileges)sc start MMSDaemon (with Administrator privileges) |