[DOCS-6830] How to restart Ops Manager when you don't have all of the local versions downloaded Created: 16/Dec/15  Updated: 27/Jul/16  Resolved: 26/Jul/16

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andrew Davidson Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.opsmanager.mongodb.com/current/tutorial/configure-local-mode/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36
Referrer: https://docs.opsmanager.mongodb.com/current/search/?query=local
Screen Resolution: 1920 x 1080
repo: REPONAME
source: tutorial/configure-local-mode


Issue Links:
Related
Participants:
Days since reply: 8 years, 9 weeks ago
Epic Link: docs-upgrade
Story Points: 1

 Description   

While https://docs.opsmanager.mongodb.com/current/tutorial/configure-local-mode/#determine-which-binaries-to-store is a start, it is important we add a sort of warning box that explains the following:

Ops Manager has pre-flight checks that will not allow Ops Manager to start in "local" mode if any version is selected in any group's Version Manager that does not have an associated binary stored locally on the Ops Manager application server.

This becomes a blocker commonly when Ops Manager is initially used for a deployment in the default internet mode, where by numerous MongoDB versions are selected in the Version Manager by default.

In this scenario, it is critical to deselect all the version (e.g. those selected via the "3.0.", "2.6." etc menus which select a large number of versions. A lot of people may assume that only versions in a managed deployment would be checked for in the pre-flight checks but they are actually looking for all versions (even those unused) enabled in the Version Manager.

While it is possible to move forward by placing all listed binaries in the releases directory, it is often easier to rectify preflight issues like the following

"Starting pre-flight checks
Managed deployments reference MongoDB versions not present in /opt/mongodb/mms/mongodb-releases/:
Group ABCDEF uses ....

by
1) Re-start Ops Manger in the default ("mongodb" mode)
2) In the UI, go to all groups listed in the pre-flight checks' Deployment > Version Manager pages, and for each
– a) De-select all versions (except those required since in use by a managed deployment)
– b) Click "Review & Deploy" to save the reduced Version Manager configuration
3) Return Ops Manager to "local" mode configuration and shut Ops Manager down
4) Place binaries in the releases directory for the minimum required (managed) mongodb versions
5) Start Ops Manager


Generated at Thu Feb 08 07:53:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.