Sep 8th, 2009, 05:23 PM
When 'Stop' fails...
... what should I do next?
I just deployed and ran a Grails app on a single instance architecture just fine. I then requested that the deployment stop, and I get the message:
* Stop : FAILED (8 minutes ago)
* Launch : COMPLETED (27 minutes ago)
And yep, the minutes are just ticking up... and all 3 components are still running, including the Apache Httpd, tcServer and MySQL.
So... what next? Is there a button I can use to kick the restart into 'aggressive' mode? As far as I can tell this is still racking up the cost of running, even while the deployment is 'Stopping', with no end in sight just yet...
Sep 8th, 2009, 05:31 PM
When 'Stop' fails... AWS Management Console succeeds
I got my instance to terminate using the regular AWS Management Console. Would be nice to have the same sort of 'terminate now, darnit!' functionality in Cloud Foundry? Or am I missing something obvious?
Sep 8th, 2009, 05:37 PM
Any chance you have saved the log?
Sep 8th, 2009, 05:42 PM
And the log is...
Attached should be the log as it is currently on the deployment that is, still, 'Stopping'
Sep 8th, 2009, 05:49 PM
Same app, cluster of tcServers and DBs, stopped just fine
Weird, but not terrible. I just deployed the same application using a number of instances and it started and stopped with no problems at all.
Anyway, keep up the great work guys, by and large this has been a tremendously straightforward experience and, imo, is just what the cloud needs!
Sep 8th, 2009, 05:51 PM
We'll figure out what went wrong and keep you posted.