S3: Storage error (500 Error)

General
1

I have been noticing s3 storage error in the logs. The instance gets captured; however, the s3 file is not uploaded to s3 bucket. In situations like this,

  1. Does Orthanc retry until it works?
  2. If S3 storage file is not uploaded to the bucket, why does Orthanc capture the instance?
  3. Is it easy to integrate Sentry into Orthanc to capture these errors?

Screenshot 2024-01-06 at 4.23.32 PM
Screenshot 2024-01-06 at 4.23.32 PM1861×141 10.5 KB

Thanks a lot.
Ernest.

2

Hi,

1: No retries
2. With the latest version of the S3 plugin, you can enable logs to possibly know more about the S3 error ("EnableAwsSdkLogs": true). The instance shall not be captured in case of failure and the error is returned to the DICOM SCU (and the DICOM SCU shall perform a retry). But we should better identify the internal errors first from the AWS logs to understand if its worth retrying - that’s the first time we see such an error message.
3. No, there’s no integration with Sentry

Best regards,

Alain.

3

Thanks a lot. I will enable the logs and capture more information.