[DOCS-7375] gen.key not matching error, et al. Created: 09/Mar/16 Updated: 03/Nov/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
redhat 6.5. Kernel 2.6.32-431.el6.x86_64 installing version 2.0.2.337-1.x86_64 of MMS. Location: https://docs.opsmanager.mongodb.com/current/tutorial/install-on-prem-from-archive/ |
||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Epic Link: | docs-troubleshooting |
| Description |
|
There should be a Troubleshoot area with common errors that one might get if installing from archive. (we are getting gen.key not matching error when we first installed MMS using rpm and later uninstall then try to re-install using tar file) There should also clarity in identifying who is running the process if mongodb-mms is started from archive. Will it be the mongodb-mms user? Will it be the username of the person that is literally running the service start command? Will it be root? (It should not be root - this is bad) |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |