-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Ops Manager
-
Labels:
-
Environment:
*Location*: https://docs.opsmanager.mongodb.com/current/reference/configuration/#mongodb-release-autodownload
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.93 Safari/537.36
*Referrer*: https://docs.opsmanager.mongodb.com/current/tutorial/configure-local-mode/
*Screen Resolution*: 1920 x 1200
*repo*: REPONAME
*source*: reference/configuration
*Location*: https://docs.opsmanager.mongodb.com/current/reference/configuration/#mongodb-release-autodownload *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.93 Safari/537.36 *Referrer*: https://docs.opsmanager.mongodb.com/current/tutorial/configure-local-mode/ *Screen Resolution*: 1920 x 1200 *repo*: REPONAME *source*: reference/configuration
-
0.3
The in the mongodb.release.autoDownload section, the path listed to the mongodb-fetch utility is incorrect. The correct path would be /opt/mongodb/mms-backup-daemon/bin.
It should also be noted here that the backup daemon expects the tgz files to be extracted. I believe this is inconsistent with automation, and is not obvious here and very easy to get wrong. mongodb-fetch would do the right thing, but is in most cases not useful since the server will not have internet access for mongodb-fetch to work, e.g. the files would be manually copied to the server via some other means.