PeterNic
03-13-2007, 05:47 PM
(How to recognize and work around defect SCR 1418)
Whenever an application fails to start due to a problem with one of its appliances, normally AppLogic returns the application to stopped state. While this is the desired result in production apps, you'd want to keep the app running in order to diagnose the problem in the faulty appliance. To do that, you start the app with '--debug' option on the command line.
This works and works fine.
Once you are happy you have fixed the problem in the appliance, you might do 'comp restart' and even 'comp restart --debug' in order to see whether the component will now start correctly from boot. This second type of restart (with --debug), AppLogic does not handle correctly: it seems to work, restarts the appliance OK, but the next time you stop the app, AppLogic will not release the appliance's volumes. As a result, the volumes will remain in use and you can no longer start the app (or least that appliance).
The only recovery is to reboot the grid.
To avoid the problem: don't use 'comp restart --debug'. Either restart the appliance without --debug (if you expect it to succeed), or restart the whole application with --debug if you still need to get in it.
Whenever an application fails to start due to a problem with one of its appliances, normally AppLogic returns the application to stopped state. While this is the desired result in production apps, you'd want to keep the app running in order to diagnose the problem in the faulty appliance. To do that, you start the app with '--debug' option on the command line.
This works and works fine.
Once you are happy you have fixed the problem in the appliance, you might do 'comp restart' and even 'comp restart --debug' in order to see whether the component will now start correctly from boot. This second type of restart (with --debug), AppLogic does not handle correctly: it seems to work, restarts the appliance OK, but the next time you stop the app, AppLogic will not release the appliance's volumes. As a result, the volumes will remain in use and you can no longer start the app (or least that appliance).
The only recovery is to reboot the grid.
To avoid the problem: don't use 'comp restart --debug'. Either restart the appliance without --debug (if you expect it to succeed), or restart the whole application with --debug if you still need to get in it.