AppLogic24 Web
AppLogic 2.4 Documentation The latest production release is AppLogic 3.0.30 Dashboard Notification Messages
Whenever important events occur on the grid, the controller posts notification messages to the grid dashboard. These messages can be obtained in one of the following ways:- looking at the grid dashboard with a browser
- retrieve the messages from the shell using the
message listcommand (it is possible to obtain that list programmatically via ssh) - receive notifications in e-mail messages
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.
| 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. | |
050_filer_status | ||
060_ha_check | HA check completed on date; the following problem(s) were found that may result in application downtime in the event of a server failure: m running applications have degraded volumes [list]. There are not enough available resources to restart components running on n server(s) [list]. o catalog class(es) with shared volumes have degraded volumes [list]. | |
060_ha_check | HA check completed on date: HA is unavailable due to the grid being a single server grid. | |
060_ha_check | HA check completed on date: HA is unavailable due to the grid having no enabled servers. | |
060_monitoring_email_nfy | Dashboard message change email notification could not be sent due to internal error - see log for details. Please contact technical support for assistance. | |
060_monitoring_email_nfy | Dashboard message change email notification could not be sent due to missing applogic configuration. Please contact technical support for assistance. | |
060_monitoring_email_nfy | Dashboard message change email notification could not be sent due to invalid severity specified within applogic configuration file. Please contact technical support for assistance. | |
060_monitoring_email_nfy | Dashboard message change email notification could not be sent due to SMTP error. Please contact technical support for assistance. | Internal condition 'filer status' occurred. This condition should not affect the operation of your grid. Please notify 3Tera support that this error has occurred and reference SCR2301. |
060_monitoring_email_post | Summary email notification could not be sent due to internal error - see log for details. Please contact technical support for assistance. | |
060_monitoring_email_post | Summary email notification could not be sent due to SMTP error. Please contact technical 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. | |
200_app_app_name | Backup of application app_name successfully completed | |
200_app_app_name | Restore of application app_name successfully completed. | |
200_appA_app_name | Backup failed to delete files from _impex volume. | |
200_appA_app_name | Restore failed to delete files from _impex volume. | |
200_appB_app_name | Prune of old app_name backups failed. | |
200_appSLAA_app_name | app_name: SLA counter collection from MON failed - policy not enforced | |
200_appSLAB_app_name | app_name: SLA cronjob cannot re-start the daemon - policy not enforced | |
200_appSLAC_app_name | app_name: SLA - all appliances are running in the appliance group appliance_group but start condition is true | |
200_appSLAD_app_name | app_name: SLA failed to start appliance appliance_name - marking as ignored | |
200_appSLAE_app_name | app_name: SLA failed to stop appliance appliance_name - marking as ignored | |
200_appSLAF_app_name | app_name: SLA - no appliances are running in the appliance group appliance_group | |
200_appSLAG_app_name | app_name: SLA policy does not match appliance group. Please re-define the policy. Until then, policy enforcement cannot occur. | |
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'. | |
400_alert_comp_name | Counter 'counter_name' in component 'comp_name' was out of range on date. Counter value is counter_value. | |
400_alert_comp_name | Multiple alarms have occured for component comp_name. Last alarm was: Counter 'counter_name' was out of range on date. Counter value is counter_value. | |
400_alert_comp_name | Alert from component 'comp_name' on date: msg | |
400_alert_comp_name | Multiple alarms have occured for component comp_name. Last alarm occured on date: msg | |
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. |
 |
|
Copyright © CA 2005-2011. All Rights Reserved.