Description of problem: when running: rhc app restart -a {app} results in: Unable to complete the requested operation due to: Failed to correctly execute all parallel operations - ["RestartCompOp"]. This is after running: rhc tidy-app -a {app} Which had resulted in: Server returned an unexpected error code: 504 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Expect app to restart Additional info:
The reference id is: 1cb97ccc289c7179981370d8428e5144
I see two separate issues: 1) The postgresql cartridge's "tidy" action appears to require that the service be running (so that it can run "vacuum". It produced this error: January 03 20:56:09 INFO oo_spawn buffer(7/) psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/lib/openshift/<UUID>/postgresql//socket//.s.PGSQL.5432"? 2) The jboss restart that happens at the end of "tidy" took too long, so that operation timed out.
To be more clear about the state of things yesterday when I made my comment, I saw that 1) the tidy operation did free of space in the gear, so that it was not near its quota, and 2) the jboss startup had succeeded (albeit outside the timeout window) and the app ( http://magickapp-magickweb.rhcloud.com ) was accessible. So in my comment I provided what appear to be the root cause(s) of the operation failure(s).
https://github.com/openshift/origin-server/pull/4494 I tried to address at least the postgresql tidy issue, where the postgres is down and 'vacuum' fail in that case. I'm not sure if I can do anything for the jboss issue :-(
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/76ef3998a2fb846ffacbc7981971eae6205ff099 Bug 1053113 - Make sure postgresql is running vacuum
Checked on devenv_4247, the postgresql tidy issue has been fixed. When the postgresql in stop status, the tidy operation will not be blocked. Mark bug as verified. # rhc cartridge-stop postgresql -a php54 Using postgresql-9.2 (PostgreSQL 9.2) for 'postgresql' Stopping postgresql-9.2 ... done # rhc app-tidy php54 RESULT: php54 cleaned up