Hide Forgot
Description of problem: After stopping and restarting app, the embedded mysql/postgresql are stopped. Version-Release number of selected component (if applicable): rhc-cartridge-mysql-5.1-0.19.3-1.el6_2.noarch rhc-cartridge-postgresql-8.4-0.2.4-1.el6_2.noarch rhc-0.85.9-1.el6_2.noarch rhc-node-0.85.16-1.el6_2.x86_64 How reproducible: Always Steps to Reproduce: 1.Create an app and embed mysql/postgresql to it 2.First stop, then restart the app. 3.Check the status of embedded mysql/postgresql. Actual results: "PostgreSQL server instance is stopped" or "Mysql is stopped" Expected results: Mysql/PostgreSQL should be started. Additional info:
This is as designed. Stop stops everything. The thinking being no one wants to have to stop multiple services to stop everything. Start starts everything. Again the thinking being they probably want their app to be running. And if that's not the case they can stop individual pieces after. But restart would most often be used to retry something. And you usually know what you want to retry. Either you made a code change or a db change or whatever. And you are hoping a restart will fix it. So we leave the control on restart on an individual component level.