Troubleshooting SMTT Alarms

If a Total Events (SMTT) alarm appears on a Storage Node, it may be related to a failure that means that platform services messages cannot be delivered.

About this task

Platform services messages cannot be delivered

If the destination for platform services messages encounters an issue that prevents it from accepting platform services messages — for example, if credentials are updated on the destination such that StorageGRID Webscale can no longer authenticate to the destination service — the operation on the bucket succeeds, but the platform services message is not delivered.

In this circumstance, the grid administrator will see a Total Events (SMTT) alarm with an error message (at site > Storage Node > SSM > Events > Last Event) that explains the nature of the issue.

Correct the issue, then reset the event count at site > Storage Node > SSM > Events > Configuration > Alarms.

Notify the tenant of the objects whose platform services messages have not been delivered. Event messages are listed in /var/local/log/bycasterr.log.

A tenant can trigger the failed replication or notification by updating the object's metadata or tags. They can resubmit the existing values to avoid making unwanted changes.

S3 Multipart Upload succeeds

If platform services are configured for an S3 bucket, an S3 multipart upload can succeed even though the associated replication or notification message cannot be delivered to the configured endpoint.

If this occurs, an alarm is raised in the Grid Management Interface on Total Events (SMTT). The Last Event message at Grid > site > Storage Node > SSM > Events displays " Failed to publish notifications for bucket-name object key " for the last object whose notification failed. Event messages are also listed in /var/local/log/bycasterr.log

A tenant can trigger the failed replication or notification by updating the object's metadata or tags. They can resubmit the existing values to avoid making unwanted changes.