Skip to main content
NetApp Knowledge Base

Is it possible to check log for S3 calls answered as 403 or 404?

  1. Last updated
  2. Save as PDF
Views:
569
Visibility:
Public
Votes:
3
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

NetApp StorageGRID

Answer

  • Individual S3 queries which are answered as 403 or 404 can be checked in the bycast-err.log in /var/local/log on the primary admin node

Example:

Oct  6 07:32:01 AMS-ADM1 NMS: |2020-10-06T07:32:01.829| ERROR   Object 'multipart-upload/test.log' not found. (MgmtApi::LocalizedValidationError)
Oct  6 07:32:01 AMS-ADM1 NMS: |2020-10-06T07:32:01.829| ERROR   /usr/local/lib/site_ruby/mgmt-api/objects/metadata.rb:108:in `rescue in find'
Oct  6 07:32:01 AMS-ADM1 NMS: |2020-10-06T07:32:01.829| ERROR   /usr/local/lib/site_ruby/mgmt-api/objects/metadata.rb:99:in `find'
Oct  6 07:32:01 AMS-ADM1 NMS: |2020-10-06T07:32:01.829| ERROR   /usr/local/mgmt-api/app/controllers/objects.rb:29:in `block in registered'

  • In 11.5 and later, S3 responses (HTTP XXX) can be viewed and graphed in Prometheus metrics page (https://ADMIN_NODE/metrics/graph) under storagegrid_s3_requests_total.

Additional Information

 

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.