[DOCS-5264] Mention that you need to manually stop the automatically started mongod service when setting up OpsManager Created: 23/Apr/15 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Joanna Cheng | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 7 years, 29 weeks ago | ||||
| Epic Link: | docs-install | ||||
| Description |
|
In Step 2 of "Prepare Each server", after installing, you need to stop the automatically-started service
Which then allows you to start it again with your own options, dbpath, etc in Step 2 of the "Deploy the Ops Manager Application Database" section |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |