| Message ID | Message text |
|---|
10diskfull | Controller boot volume is nearly full. Please take immediate action or contact 3tera technical support. |
010_grid_boot | Grid has been restarted on date. Processing reboot instructions... |
010_grid_boot | Grid has been restarted reason on date. Processing reboot instructions... |
010_grid_boot | Grid has been restarted reason on date. Restarting applications... |
010_grid_boot | Grid has been restarted reason on date. Application restart aborted by operator. |
010_grid_boot | Grid has been restarted reason on date. No applications were started because reason. |
010_grid_boot | Grid has been restarted reason on date. Grid restart completed on date. |
010_grid_boot | Grid has been restarted reason on date. Attempting application restart with m of n servers unavailable. |
010_grid_boot | Grid has been restarted reason on date. Application restart was aborted due to internal error; see log for details. |
020_grid_start | m of n applications started. x applications failed to start. y applications are not restartable. z applications are currently starting (start progress%). |
020_grid_start | Waiting for n more servers to rejoin the grid (timeout in t seconds) |
050_metering_collect | Grid metering data could not be collected due to internal error, please contact support for assistance. |
050_metering_report | Grid metering data could not be sent to 3tera due to internal error, please contact support for assistance. |
070_vol_maint | Failed to initiate volume check on date because another volume check was in progress. Please contact 3tera technical support for assistance. |
070_vol_maint | Volume check completed on date. Volume maintenance is required. Found x inaccessible volumes, y degraded volumes, z orphan volumes. |
100_srv_server_name | Lost connection to server 'server name' on date. |
100_comp_server_name | Server 'server name' was disabled on date because it has gone down too often within the specified time period. |
300_comp_comp_name | Restarted appliance 'comp_name' on date due to server failure. |
300_comp_comp_name | Restarted appliance 'comp_name' on date due to appliance failure. |
300_comp_comp_name | Failed to restart appliance 'comp_name' on date after server failure. Failed to allocate resources for appliance. |
300_comp_comp_name | Failed to restart appliance 'comp_name' on date after server failure. Appliance restart failed. |
300_comp_comp_name | Failed to restart appliance 'comp_name' on date after appliance failure. |
300_comp_comp_name | Restarting appliance 'comp_name' on date due to server failure. |
300_comp_comp_name | Restarting appliance 'comp_name' on date due to appliance failure. |
300_comp_comp_name | Appliance 'comp_name' restart failed at date. Appliance has failed too often within the specified time period. |
300_comp_comp_name | Appliance 'comp_name' failed due to server lost at date. Lost connection to server 'server name'. |
500_oem_error_tnc | Terms of use link is not configured. Please contact your service provider or support@3tera.NOSPAM.com |
800_oem_config | The OEM configuration file for this grid is missing or not readable; see log for details. Your support links and other provider-specific information displayed on the dashboard may be incorrect, as the OEM configuration has not been applied. This error does not affect the operation of your grid. Please contact your service provider for assistance. |
Sep 7 - AppLogic 2.1 has been officially released! See 
Note that the message ID or text may vary slightly (e.g., number of apps failed to restart will not be listed at all if all apps restarted OK). Also, with each release of AppLogic we are improving the messages, so they will be changing in the future as well. When upgrading to a new version of AppLogic, if you use an automated system to collect and parse the notification messages, please verify that it recognizes all cases that you require.