Event Listing
The following table list all of the events that can be triggered on the system. The numbers in the Message column are simply placeholders for other strings that may be passed (things like entity names).
Event Name |
Type |
Message |
NONE |
DEBUG |
None |
CREATED |
INFORMATIONAL |
{0} {1} created by {2}{3} |
ADDED |
INFORMATIONAL |
{0} {1} added by {2}{3} |
CANCELLED |
INFORMATIONAL |
{0} {1} cancelled by {2}{3} |
UPDATED |
INFORMATIONAL |
{0} {1} updated by {2}{3} |
DELETED |
INFORMATIONAL |
{0} {1} deleted by {2}{3} |
REMOVED |
INFORMATIONAL |
{0} {1} removed by {2}{3} |
CREATE_FAILED |
ERROR |
Failed to create {0} {1} by {2}{3} |
ADD_FAILED |
ERROR |
Failed to add {0} {1} by {2}{3} |
UPDATE_FAILED |
ERROR |
Failed to update {0} {1} by {2}{3} |
DELETE_FAILED |
ERROR |
Failed to delete {0} {1} by {2}{3} |
REMOVE_FAILED |
ERROR |
Failed to remove {0} {1} by {2}{3} |
NO_AVAILABLE_STORAGE_ON_NODE |
ERROR |
Node {0} has no available storage |
COMPONENT_MISSING |
NOTICE |
Component {0} {1} is missing in the node {2}. If this is expected, node refresh may be used to reconcile the missing component |
SOFTWARE_VERSION_CHANGED |
INFORMATIONAL |
Software version has changed from {0} to {1} on node {2} |
SOFTWARE_UPDATE_STARTED |
INFORMATIONAL |
Updating {0}to {1} |
SOFTWARE_UPDATE_SUCCESS |
INFORMATIONAL |
Updated {0}to {1} |
SOFTWARE_UPDATE_FAILED |
Failed to update {0}to {1} |
|
LICENSE_STATE_CHANGED |
INFORMATIONAL |
The license state changed |
LICENSE_ACTIVATED |
INFORMATIONAL |
License activated successfully |
LICENSE_ACTIVATION_FAILED |
ERROR |
License activation failed{0} |
EVAL_ABOUT_TO_EXPIRE |
WARNING |
Your evaluation will end within {0} days, please contact support |
EVAL_EXPIRED |
ERROR |
A license is required to operate beyond {0} days after installation. Protocol access has been disabled. Please contact support to resolve the situation |
LICENSE_ABOUT_TO_EXPIRE |
WARNING |
Your {2} license is expiring within {1} days, in order to maintain product functionality and not lose protocol access, please contact support |
LICENSE_EXPIRED |
ERROR |
Your {1} license has expired. The product functionality has been reduced, you can no longer access your data over supported protocols. Please contact support immediately to re-enable access |
EXPIRED_LICENSE_IN_GRACE |
WARNING |
Your expired {3} license has entered a {1} day grace period. There are {2} days remaining before you can no longer access your data over supported protocols. Please contact support to obtain a new license |
METERED_LICENSE_IN_GRACE |
Your metered license with activation ID {0} which is reporting usage to {1} has entered a {2} day grace period due to successive failures to communicate with the license server. There are {3} days remaining before you can no longer access your data over supported protocols. If communication with the license server is re-established within this period your system will automatically return to normal operation. If the condition persists, please contact support |
|
LICENSE_IN_GRACE_ABOUT_TO_EXPIRE |
WARNING |
Your expired {3} license has {1} days remaining in a {2} day grace period. Please contact support to obtain a new license |
LICENSE_ABOUT_TO_ENTER_GRACE |
WARNING |
Your {3} license will enter a grace period in {1} days. After that, you will have {2} days to renew your license |
LICENSING_MISCONFIGURED |
Your licensing is improperly configured. When using capacity-based licensing you need either a File license or both a File and Object license. System protocols are being disabled. Please contact support. |
|
BORROWING_LICENSE_EXPIRED |
Your {1} license has expired. All used {1} storage is now counted against your licensed {2} |
|
BORROWING_LICENSE_ABOUT_TO_EXPIRE |
Your {1} license is expiring soon, after which time all used {3} storage will be counted against your licensed {2} |
|
ACTUAL_ALLOCATED_CAPACITY_EXCEEDED |
You have exceeded the {1}TB of licensed {2}. You are borrowing {3} from {4} |
|
ALLOCATED_CAPACITY_EXCEEDED |
ERROR |
You have exceeded the {1}TB of licensed {3} and have entered a grace period. You have {2} days remaining to reduce storage usage |
ALLOCATED_CAPACITY_APPROACHING_LIMIT |
WARNING |
You are currently using {1}% of the {2}TB of licensed {3} |
OVER_CAPACITY_GRACE_ABOUT_TO_EXPIRE |
WARNING |
The over-capacity grace period is nearing expiration. You have {2} days remaining to reduce storage usage |
OVER_CAPACITY_LICENSE_VIOLATION |
You have exceeded the {1}TB of licensed {3} for over {2} days. System protocols are being disabled |
|
USER_PASSWORD_CHANGED |
INFORMATIONAL |
The user password changed |
MGMT_STARTED |
INFORMATIONAL |
Management started |
MGMT_STARTED_FROM_RESTORE |
INFORMATIONAL |
Management started from restore |
MGMT_GENERIC_EVENT |
{0} |
|
NODE_MODE_ISSUE |
NOTICE |
Node ''{0}'' mode changed to OFFLINE. {1} |
CLUSTER_FAILOVER |
NOTICE |
{0} is taking over as the primary Anvil |
CLUSTER_SPLIT_BRAIN |
ERROR |
Critical error {0} in the Anvil cluster state has been identified. The Anvil can not continue to serve, please call support. |
CLUSTER_REPLICATION_EVENT |
INFORMATIONAL |
Cluster replication state changed to {0} |
DD_CLUSTER_PLANNED_SHUTDOWN |
INFORMATIONAL |
Anvil cluster shut down. Reason: {0} |
DD_CLUSTER_PLANNED_SHUTDOWN_FAILED |
ERROR |
Failed to shut down Anvil cluster |
NETWORK_LDAP_UNREACHABLE |
ERROR |
LDAP is unreachable |
NETWORK_NTP_UNREACHABLE |
ERROR |
NTP is unreachable |
VOLUME_STATE_CHANGED |
INFORMATIONAL |
{0} ''{1}'' changed state to ''{3}'' |
VOLUME_DECOMMISSION_EVENT |
INFORMATIONAL |
{0} {1} decommissioned |
VOLUME_ASSIMILATION_EVENT |
INFORMATIONAL |
Volume assimilation event |
VOLUME_CONFIG_TEST_FAILED |
ERROR |
Volume configuration test failed from ''{0}'' on node ''{1}'' to ''{2}'' on volume ''{3}''. Output: {4} |
VOLUME_CONFIG_TEST_ALL_FAILED |
ERROR |
Volume configuration test failed from node ''{0}'' to volume ''{1}'' over all IP addresses. Output: {2} |
VOLUME_CLONE_TEST_FAILED |
ERROR |
Volume offloaded clone check failed. Reason: {0} |
HW_NIC_LINK_EVENT |
NOTICE |
NIC event: NIC {0} {1} |
HW_DRIVE_FAILED |
ERROR |
Physical drive {0} failed |
HW_RAID_EVENT |
NOTICE |
RAID event occurred |
HW_FAN_FAILED |
ERROR |
Fan failed |
HW_PSU_FAILED |
ERROR |
Power supply failed |
HW_FRU_EVENT |
NOTICE |
{0} hardware device {1} |
VASA_VAAI_PROVIDER_EVENT |
INFORMATIONAL |
VASA VAAI provider event |
PORTAL_EXPORT_FAILED |
ERROR |
Data Portal ''{0}'' encountered problems while trying to export path ''{1}'' |
PORTAL_UNEXPORT_FAILED |
ERROR |
Data Portal ''{0}'' encountered problems while trying to unexport path ''{1}'' |
SUPPORT_CALL_HOME_EVENT |
INFORMATIONAL |
Support call home event |
SHARE_QUOTA_WARNING |
WARNING |
Share quota is running out, crossed {0}% |
SHARE_QUOTA_EXCEEDED |
ERROR |
Share quota exceeded |
SHARE_RESTORED |
INFORMATIONAL |
Share {0} restored from snapshot {1} |
SHARE_RESTORE_FAILED |
ERROR |
Failed to restore share {0} from snapshot {1} |
SHARE_SNAPSHOT_CREATED |
INFORMATIONAL |
Created snapshot {0} for share {1} |
SHARE_SNAPSHOT_CREATE_FAILED |
ERROR |
Failed to create snapshot {0} for share {1} due to error {2} |
SHARE_SNAPSHOT_DELETED |
INFORMATIONAL |
Deleted snapshot {0} for share {1} |
SHARE_SNAPSHOT_DELETE_FAILED |
ERROR |
Failed to delete snapshot {0} for share {1} due to error {2} |
SHARE_CLONED |
INFORMATIONAL |
Share {0} cloned |
SHARE_CLONE_FAILED |
ERROR |
Share {0} clone failed |
ASSIMILATION_SUCCESS |
INFORMATIONAL |
Assimilation of {0} {1} by {2} completed successfully{3} |
ASSIMILATION_FAILED |
ERROR |
Failed to assimilate data from {0} {1} by {2}{3} |
ASSIMILATION_STOPPED |
ERROR |
Assimilation from {0} {1} by {2} has been stopped for user remediation{3} |
ASSIMILATION_CANCELLED |
INFORMATIONAL |
Assimilation from {0} {1} by {2} has been cancelled{3} |
READ_LATENCY_THRESHOLD_CROSSED |
WARNING |
{0} {1} exceeded read latency threshold |
WRITE_LATENCY_THRESHOLD_CROSSED |
WARNING |
{0} {1} exceeded write latency threshold |
SHARE_PRUNING |
INFORMATIONAL |
Share {0} pruned |
SHARE_PRUNING_BLOCKED |
ERROR |
Share {0} pruning blocked. Last Pruned:{1} |
VOLUME_EVICTION_FAILED |
ERROR |
Attempt to evict files from Volume {0} failed |
INVALID_COMB_STRUCTURE |
ERROR |
volume {0} Invalid COMB Structure |
NO_REGISTERED_MOVER |
ERROR |
No registered mover in Data Manager |
NO_REGISTERED_STORAGE_VOLUME |
ERROR |
No registered Storage Volume in Data Manager |
PDDM_EXITED |
ERROR |
Data Manager Exited upon detecting inconsistency in data or configuration |
PDDM_KILLED_DI |
ERROR |
Mover with ID {1} terminated |
MODELER_SHARE_SWEEP_COMPLETED |
INFORMATIONAL |
Modeler share sweep of share {0} completed |
PDDM_RESTART |
INFORMATIONAL |
Data Manager Restarted |
COLLECTIONS_ENTER |
INFORMATIONAL |
Inode {1} entered collection {2} |
COLLECTIONS_LEAVE |
INFORMATIONAL |
Inode {1} exited collection {2} |
DISK_USAGE_LIMIT_WARNING |
WARNING |
Disk usage near limit on {0}:{1} with only {2} available. |
DISK_USAGE_LIMIT_EXCEEDED |
ERROR |
Disk usage limit EXCEEDED on {0}:{1} with only {2} available. |
SALT_NOT_FUNCTIONAL |
ERROR |
Salt is not functional. Reason: {0} |
MISSING_DATA_MOVER |
ERROR |
No data mover detected. Please add a DSX node to the installation. |
MISSING_CLOUD_MOVER |
ERROR |
No cloud mover detected. Please add a DSX node to the installation. |
MISSING_STORAGE_VOLUME |
ERROR |
No writable backend storage volumes. At least 1 writable volume must be added before using the namespace. |
DATA_COPY_TO_OBJECT_SUCCESS |
INFORMATIONAL |
Data copy to object from ''{0}'' in share ''{1}'' to bucket ''{2}'' and path ''{3}'' at ''{4}'' succeeded |
DATA_COPY_TO_OBJECT_FAILED |
ERROR |
Data copy to object from ''{0}'' in share ''{1}'' to bucket ''{2}'' and path ''{3}'' at ''{4}'' failed |
BACKUP_NOT_SCHEDULED |
WARNING |
Metadata and configuration backup is not configured |
BACKUP_FAILED |
ERROR |
Metadata and configuration backup to {0}:{1} failed. Schedule name: {2}. |
BACKUP_COMPLETED |
INFORMATIONAL |
Metadata and configuration backup to {0}:{1} completed. Schedule name: {2}. |
BACKUP_CREATION_FAILED |
ERROR |
Could not start metadata and configuration backup to {0}:{1}. Schedule name: {2}. |
CTDB_NODE_FAILURE |
ERROR |
CTDB node {0}@{1} status is {2} |
CTDB_NOT_RESPONDING |
ERROR |
CTDB service is not responding: {0}. Please contact support to resolve the situation. |
CTDB_IN_RECOVERY |
WARNING |
CTDB service is in recovery mode. Please contact support to resolve the situation. |
KMS_OPERATION_CHECK_FAILED |
ERROR |
KMS operation check failed. Reason: {0} |
GFS_PARTICIPANT_ADDED |
INFORMATIONAL |
GFS participant added to share ''{0}'' for site ''{1}'' |
GFS_PARTICIPANT_ADD_FAILED |
ERROR |
Failed to add GFS participant to share ''{0}'' for site ''{1}''. Reason: {2} |
GFS_PARTICIPANT_REMOVED |
INFORMATIONAL |
GFS participant removed from share ''{0}'' for site ''{1}'' |
GFS_PARTICIPANT_REMOVE_FAILED |
ERROR |
Failed to remove GFS participant from share ''{0}'' for site ''{1}''. Reason: {2} |
REPLICATION_PORT_CHECK_FAILED |
ERROR |
Share replication port check failed. Details: {0} |
GFS_PARTICIPANT_OPER_STATE_CHANGED |
GFS participant operational state changed to state ''{0}''. Reason: {1} |
|
METADATA_REPLICATION_ISSUE |
Metadata replication issue for share ''{0}'' and site ''{1}''. Reason: {2} |
|
DATA_REPLICATION_ISSUE |
Data replication issue for share ''{0}'' and site ''{1}''. Reason: {2} |
|
REPLICATION_LATENCY_THRESHOLD_EXCEEDED |
Replication {1} latency of {2} seconds exceeds the threshold for participant {0} |
|
MISSING_SHARED_OBJECT_STORAGE_VOLUME |
No healthy object storage volumes for share replication between share ''{0}'' and site ''{1}''. |
|
CAPACITY_HEARTBEAT_DISABLED |
Capacity heartbeat reporting disabled while operating under a capacity-based license |
|
MOVER_CONNECTED |
INFORMATIONAL |
Mover ''{0}'' (uuid: ''{1}'') connected from ip address ''{2}'' |
MOVER_UNKNOWN |
WARNING |
Unknown mover (uuid: ''{1}'') attempted to connect from ip address ''{2}'' |
MOVER_BAD_IP |
Mover ''{0}'' (uuid: ''{1}'') connected from an invalid data-channel ip address ''{2}'' |
|
MOVER_DROPPED |
ERROR |
Dropped mover ''{0}'' (uuid: ''{1}'') due to heartbeat failure |
MOVER_AT_CAPACITY |
Mover ''{0}'' (uuid: ''{1}'') at ''{2}'' is over-utilized. Data mobility performance may be suboptimal. If this persists, consider adding memory or CPU resources to this mover, or adding another DSX |
|
CAPACITY_THRESHOLD_PASSED |
WARNING |
'{1}'' has exceeded its {2} capacity threshold of {3}% ({4}/{5} used). {7,choice,0#The volume will be less likely to be the target of new data and data mobility. |
SHARE_EVENTS_PROCESSING |
Event processing in progress for share ''{0}''. Volume removal may be affected until all events are processed. Events processed: {1}/{2} |
|
SHARE_EVENTS_PROCESSED |
Event processing completed for share ''{0}'' |
|
SHARE_EVENT_PROCESSING_BLOCKED |
Event processing blocked for share ''{0}''. Please contact support |
|
FAILURE_REPORTING_LICENSED_USAGE |
Failure reporting usage for activation ID {0} to license server at {1} |
|
INVALID_ADDITIONAL_ADDRESS |
Additional IP address(es) mis-configured. Cause: {1} |
|
KEYTAB_MISMATCH |
Kerberos keytab file on Node ''{0}'' is out of sync, and attempts to re-sync it have failed. Please contact support. |
|
AD_WITHOUT_NTP |
When Active Directory is joined, NTP should also be configured |
|
NTP_NOT_SYNCHRONIZED |
The clock between ''{0}'' and ''{1}'' is not synchronized. Check for correct configuration and networking issues |
|
AD_DC_OUT_OF_TIME_SYNC |
Active Directory Domain Controllers out of time sync with product. Product time: ''{0}''. Out of sync DCs: {1} |
|
AD_COMPUTER_ISSUE |
Problem found with Active Directory computer account ''{0}''. Cause: {1}. Either remedy in Active Directory or leave and re-join Active Directory. |
|
AD_CACHE_FLUSH_SUCCESS |
Active Directory cache flush successful. |
|
AD_CACHE_FLUSH_FAILED |
Active Directory cache flush failed. Reason: {0}" |
|
IDMAPD_SYNC_ISSUE |
INFORMATIONAL |
{0} |
REPLICATION_WITHOUT_NTP |
The site ''{0}'' at {1} is participating in one or more global filesystems and needs NTP configured |
|
REPLICATION_CLOCK_OUT_OF_SYNC |
The site ''{0}'' at {1} is participating in one or more global filesystems and its clock differs by {2} seconds with this site''s clock. Ensure that both sites are properly configured with NTP. |
|
AD_SERVER_ISSUE |
Problem found with Active Directory server value: {0}. Either clear the list of AD servers, or update it to contain only valid and reachable servers. |
|
SERVICE_OPER_STATE_ISSUE |
NOTICE |
{0} ''{1}'' operational state changed to ''{2}''. {3} |
OBJECT_VOLUME_IO_TEST_FAILED |
Object volume I/O test failed from node ''{0}'' to volume ''{1}''. Cause: {2} |
|
OBJECT_VOLUME_IO_TEST_ALL_FAILED |
Object volume I/O test failed from all nodes to volume ''{0}''. See individual failures for causes. |
|
OBJECT_VOLUME_RESERVATION_OLD |
NOTICE |
An old reservation exists on object volume ''{0}'' for site ''{1}''. The last refresh of the reservation was at {2}. The site at {3} {4,choice,1#does not respond |
DNS_ISSUE |
ERROR |
Domain name resolution {0}. {1} |
CLUSTER_DEGRADED |
ERROR |
HA cluster state degraded. Reason: {0} |
OBJECT_VOLUME_GC_COMPLETED |
INFORMATIONAL |
{3} |
OBJECT_VOLUME_GC_FAILED |
ERROR |
{3} |
OBJECT_VOLUME_GC_CANCELLED |
INFORMATIONAL |
{3} |
OBJECT_VOLUME_GC_BLOCKED |
GC is blocked for volume {0} due to {1} |
|
ECGROUP_ARRAY |
INFORMATIONAL |
ECGROUP array : {0} |
ECGROUP_MOUNTPOINT |
INFORMATIONAL |
ECGROUP mountpoint : {0} |
ECGROUP_STORAGE |
INFORMATIONAL |
ECGROUP storage : {0} |
OSV_QUORUM_IN_FLUX |
Object volume quorum undergoing changes. Content database should resolve the issue as it discovers the site that is joining or leaving. |
|
OSV_HMDB_REPLICATION_OUT_OF_SYNC |
Object volume content database replication out of sync. Garbage collection disabled. Please contact support. |
|
OSV_SITE_TO_SITE_CONN_FAILED |
Network connection failure to Object volume content database at remote site anvil {2}:9298 (TCP). Check network configuration: {3} |
|
OSV_CSP_CONN_FAILED |
Object volume content database cloud service provider connection failure: {0} |
|
PROMETHEUS_DEGRADED |
Prometheus exporters in degraded state on node {0} |
|
OSV_HMDB_INSUFFICIENT_GC_MEMORY |
The system is unable to initiate Object Volume Garbage Collection. Contact support for additional help: Insufficient allocated memory for Object volume content database; {0} bytes required, {1} bytes available; filter false positive rate: {2} |
|
QUORUM_DEVICE_CONFIGURED |
Quorum Device configured |
|
QUORUM_DEVICE_UNCONFIGURED |
Quorum Device unconfigured |
|
QUORUM_DEVICE_UNHEALTHY |
Quorum Device is unhealthy with respect to Anvil {0} |
|
MISSING_COMB_STRUCTURE |
ERROR |
Storage volume is missing a comb structure for MDSI ''{0}'' ({1}). Will re-attempt creation. |
KERBEROS_SYNC_FAILURE |
Failed to synchronize Kerberos configuration to node {0} |
|
KERBEROS_SHARE_WITH_UNJOINED_AD |
Share ''{0}'' has Kerberos security options, but AD is not joined |
|
NFS_LAYOUT_ERROR_STALE |
ERROR |
Data I/O error for share ''{1}'': {2} recent attempts to access data with stale file handle. {3} |
NFS_LAYOUT_ERROR_NXIO |
ERROR |
Data I/O error for share ''{1}'': {2} recent attempts to access an unavailable volume. {3} |
NFS_LAYOUT_ERROR_IO |
ERROR |
Data I/O error for share ''{1}'': {2} recent attempts to access files whose underlying instances could not be found. {3} |
NFS_LAYOUT_ERROR_ACCESS |
ERROR |
Data I/O error for share ''{1}'': {2} recent denied volume access attempts. {3} |
S3_MULTIPART_UPLOAD_ABORTED |
{0} S3 multipart {1,choice,1#upload |
|
OSV_HMDB_DEGRADED_BLOOM_FILTER_ALLOCATED |
The system is unable to initiate Object Volume Garbage Collection at full efficiency. Contact support for additional help: Insufficient allocated memory for Object volume content database; {2} bytes required, {3} bytes available; filter false positive rate: {0}, preferred rate: {1} |
|
KERBEROS_CLUSTER_UNHEALTHY |
Cluster misconfigured for Kerberos data portal access: {0} |
|
KERBEROS_SHARE_WITH_NO_NFS_SPNS |
Share ''{0}'' has Kerberos security options, but NFS SPNs are not configured |
|
CLUSTER_MISCONFIGURED |
A quorum device must be configured, or a DSX node must be added in order to maintain high availability under all scenarios. |
|
NoSuchBucket |
NOTICE |
S3 service: a Hammerspace-created bucket directory is missing on disk (for example, removed over NFS/SMB). Reported once per S3 service restart; audit message that does not clear. |
NoSuchContainer |
NOTICE |
S3 service: a Hammerspace-created bucket container directory is missing on disk (for example, removed over NFS/SMB). Reported once per S3 service restart; audit message that does not clear. |
NVMEOF_PATH_DEGRADED |
WARNING |
NVMe-oF path degraded (controller stuck connecting): {0}, {1}, {2}, {3}, {4} |
NVMEOF_PATH_LOST |
WARNING or CRITICAL |
NVMe-oF path lost: {0}, {1}, {2}, {3}, {4} |