Description of problem: Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. rhc app create test ruby-1.9 mongodb-2.4 2. At https://mms.mongodb.com create account and download monitor-agent zip/tar 3. copy settting.py to the $APP_DIR/.openshift/mms 3. rhc cartridge add 10gen-mms-agent-0.1 -a test Actual results: Failed to execute: 'control start' for /var/lib/openshift/52fe2975bd61cb1cb900000c/10gen-mms-agent Expected results: Cartridge should be embeded without error Additional info: Problem seems to be related which changed layout of the monitoring agent zip/tar which can be downloaded after registering for MMS. Now the settings.py doesn't contain 'secret_key' attribute
It's also reproduced on INT(devenv_4382).
It can work for old settings.py, but failed to work for new settings.py, please refer to the following results: 1. For the old settings.py 1) rhc app create test ruby-1.9 mongodb-2.4 2) copy old settting.py to the $APP_DIR/.openshift/mms 3) rhc cartridge add 10gen-mms-agent-0.1 -a test Adding 10gen-mms-agent-0.1 to application 'test' ... done 10gen-mms-agent-0.1 (10gen Mongo Monitoring Service Agent) ---------------------------------------------------------- Gears: Located with mongodb-2.4, ruby-1.9 Monitoring URL: https://mms.mongodb.com/ 10gen-mms-agent added. Please configure your mongodb host at https://mms.mongodb.com/ to start monitoring performance data. Monitoring URL: https://mms.mongodb.com/ 2. For the new settings.py 1) rhc app create test ruby-1.9 mongodb-2.4 2) At https://mms.mongodb.com create account and download monitor-agent zip/tar 3) copy new settting.py to the $APP_DIR/.openshift/mms 4) rhc cartridge add 10gen-mms-agent-0.1 -a test Adding 10gen-mms-agent-0.1 to application 'test1' ... Starting 10gen-mms-agent cartridge Failed to execute: 'control start' for /var/lib/openshift/53016eed6cec0e13ab000083/10gen-mms-agent
Created attachment 863946 [details] old settings.py file
Created attachment 863947 [details] new settings.py file
BTW: If adding the secret_key filed back to the new settings.py file, then we can embed 10-gen cartridge to application with mongodb.
There is a Trello card[1] for updating mms cartridge to newer version that should fix this bug. I think chunchen workaround (adding secret_key into new settings.py) is reasonable to fix this bug in a meantime. Moving this off the blocker list but keeping this bug open for the Trello card completetion (Dan?) [1] https://trello.com/c/8OD69SJS/142-update-10gen-mms-agent-cartridge-due-to-settings-py-layout-changes
I was hoping we would fix this before releasing. All new users would be affected right?
(In reply to Dan McPherson from comment #7) > I was hoping we would fix this before releasing. All new users would be > affected right? I think all new 10gen users will be affected unless they add their seceret key field manually to the settings.py file. If we want to delay the fix, we may fix the docs firstly or highlight it in release notes about the work around.
*** Bug 1071598 has been marked as a duplicate of this bug. ***
I think we can close this one, cause the new settings.py is not present in the current tarball. Instead the new tarball contains now only two files. Those are: mongodb-mms-monitoring-agent, monitoring-agent.config Closing this one. Was reported by me and also fixed and I believe this scenario is not valid anymore.
Is there new documentation on how to use the monitoring-agent.config format? Right now I think the "10gen Mongo Monitoring Service Agent" still expects settings.py file. You can still get the legacy .tar.gz or .zip file from https://mms.mongodb.com/setup/monitoring#monitoringAgent which contains settings.py file by clicking other linux and using the links found here: "If you are using Kerberos authentication, or your Monitoring Agent must connect to the internet via proxy, you will need to continue to use our legacy Python Monitoring Agent. You may download a zip or tar.gz file. See the docs for installation instructions." I've tried adding my apikey to the settings.py file and following the documentation but i'm still getting the error: "Unable to complete the requested operation. Show less Starting 10gen-mms-agent cartridge 10gen-mms-agent added. Please configure your mongodb host at https://mms.mongodb.com/ to start monitoring performance data. Monitoring URL: https://mms.mongodb.com/ Failed to execute: 'control start' for /var/lib/openshift/53319fea5973ca7c8600062b/10gen-mms-agent" Steps to reproduce: - create an application with node.js and mongodb... - create .openshift/mms/settings.py from the legacy archive and modify it so that mms_key="myapikey" is set - try to add "10gen Mongo Monitoring Service Agent" from the openshift web interface Actual results: "Unable to complete the requested operation. Show less Starting 10gen-mms-agent cartridge 10gen-mms-agent added. Please configure your mongodb host at https://mms.mongodb.com/ to start monitoring performance data. Monitoring URL: https://mms.mongodb.com/ Failed to execute: 'control start' for /var/lib/openshift/53319fea5973ca7c8600062b/10gen-mms-agent" Expected results: - not an error I think the bug is that the package still expects a settings.py file in .openshift/mms/settings.py I know this is closed but just ran into this issue and not sure how to get MMS up and running.