The following messages are displayed during and after grid startup or recovery:
|
Message ID |
Severity |
Message text |
Reason |
Action |
|---|---|---|---|---|
|
010_grid_boot |
Info |
Grid has been restarted on date. Processing reboot instructions. |
CA AppLogic is processing reboot instructions after grid was restarted. |
No action is required. This message is informational. |
|
010_grid_boot |
Info |
Grid has been restarted reason on date. Processing reboot instructions. |
CA AppLogic is processing reboot instructions after grid was restarted. |
No action is required. This message is informational. |
|
010_grid_boot |
Info |
Grid has been restarted reason on date. Restarting applications. |
CA AppLogic is restarting previously running applications after a grid reboot. |
No action is required. This message is informational. |
|
010_grid_boot |
info |
Grid has been restarted reason on date. Application restart aborted by administrator. |
CA AppLogic is not restarting previously running applications after a grid reboot due to abort by administrator. |
No action is required. This message is informational. |
|
010_grid_boot |
info |
Grid has been restarted reason on date. No applications were started because reason. |
CA AppLogic is not restarting previously running applications after a grid reboot due to the reason specified. |
Contact CA Support. |
|
010_grid_boot |
info |
Grid has been restarted reason on date. Grid restart completed on date. |
A grid restart was completed. |
No action is required. This message is informational. |
|
010_grid_boot |
info |
Grid has been restarted reason on date. Attempting application restart with m of n servers unavailable. |
A grid restart was completed and previously running applications are attempted to be restarted on m out of n previously available servers. One or more previously available servers have not rejoined the grid after a reboot. |
Determine the state of the servers, contact CA Support. |
|
010_grid_boot |
alert |
Grid has been restarted reason on date. Application restart was aborted due to internal error; see log for details. |
A grid restart was completed. CA AppLogic failed to restart previously running applications. |
Check /var/log/messages on the controller for any error messages. |
|
010_grid_start |
info |
Starting grid recovery at time |
Grid recovery has been initiated after a controller VM restart |
No action is required. This message is informational. |
|
020_grid_progress |
info |
Waiting for N more servers to rejoin grid (timeout in M seconds) |
Grid recovery has been initiated after a controller VM restart. |
No action is required. This message is informational. |
|
020_grid_progress |
info |
Grid recovery in progress. |
Grid recovery is in progress after a controller VM restart. |
No action is required. This message is informational. |
|
020_grid_progress |
info |
Grid recovery in progress: There were N active application(s) when the controller went down. M application(s) have been recovered. The state of P application(s) has been reacquired. Recovering Q application(s). |
Grid recovery is in progress after a controller VM restart. |
No action is required. This message is informational. |
|
020_grid_progress |
info |
Grid recovery completed on date: No applications were recovered because there were no previously running applications. |
Grid recovery has completed after a controller VM restart. |
No action is required. This message is informational. |
|
020_grid_progress |
info |
Grid recovery completed on date: There were N active application(s) when the grid controller went down. M application(s) have been recovered. The state of P application(s) has been reacquired. |
Grid recovery has completed after a controller VM restart. |
No action is required. This message is informational. |
|
020_grid_progress |
info |
Grid recovery completed on date: There were N active application(s) when the grid controller went down. M application(s) were not recovered because grid recovery was aborted by administrator. |
Grid recovery has completed after a controller VM restart. Some applications were not recovered due to an abort by grid administrator. |
No action is required. This message is informational. |
|
020_grid_progress |
alert |
Grid recovery in progress: There were N active application(s) when the controller went down. M application(s) failed to be recovered. |
Grid recovery in progress after a controller VM restart. Some applications were not recovered due to error. |
Check /var/log/messages on the controller for any error messages. |
|
020_grid_progress |
alert |
Grid recovery completed on date: There were N active application(s) when the grid controller went down. M application(s) failed to be recovered. |
Grid recovery has completed after a controller VM restart. Some applications were not recovered due to error. |
Check /var/log/messages on the controller for any error messages. |
|
030_grid_failure |
alert |
Grid recovery was aborted due to internal error: see controller system log for details. |
Grid recovery has aborted after a controller VM restart. |
Check /var/log/messages on the controller for any error messages. |
|
030_grid_srv_failed |
alert |
Grid recovery may not be successful. Some servers failed to connect in time. |
A failure is possible during grid recovery as one or more servers failed to rejoin the grid. |
Contact CA Support. |
|
030_grid_vol_failed |
alert |
Grid recovery failure: Failed to recover volume state. See controller system log for details. |
Grid recovery has failed after a controller VM restart. CA AppLogic failed to recover state of a volume required for recovery. |
Check /var/log/messages on the controller for any error messages. |
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|