You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[31mERROR [0m [2023-09-27T17:39:29Z] Completed in 3.748316ms /images/k20C47A1mzsp-9YHE5kDYI4Dsve91w-2VydCnDTBWPw/rs:fit:694:521::true:ce:0:0/bg:50:50:50/plain/s3://angus-active-storage-production/q9m9jbux720b7rkel4men6k0pbf8 [1mrequest_id[0m=LUnWMvlwKsZNRxegFSqhM [1mmethod[0m=GET [1mstatus[0m=500 [1mclient_ip[0m=66.249.66.34 [1merror[0m="Can't download source image: Get "s3://angus-active-storage-production/q9m9jbux720b7rkel4men6k0pbf8": RequestError: send request failed\ncaused by: Get "https://angus-active-storage-production.s3.af-south-1.amazonaws.com/q9m9jbux720b7rkel4men6k0pbf8": read tcp 172.31.17.55:51728->3.5.228.204:443: read: connection reset by peer"
The problem is that because it's a generic 500 error, it's triggering a CloudWatch alarm, but actually, it's just a transient network error which doesn't require further investigation, so it's just creating noise.
I checked the documentation but I couldn't find any retry settings so I'm wondering how we could handle these errors. The request was completed in 3.7ms so there would have been enough time to retry it.
Is a retry logic on the roadmap?
If not then would it make sense to use a different error code for these errors?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The following error was thrown by imgproxy:
The problem is that because it's a generic 500 error, it's triggering a CloudWatch alarm, but actually, it's just a transient network error which doesn't require further investigation, so it's just creating noise.
I checked the documentation but I couldn't find any retry settings so I'm wondering how we could handle these errors. The request was completed in 3.7ms so there would have been enough time to retry it.
Is a retry logic on the roadmap?
If not then would it make sense to use a different error code for these errors?
Beta Was this translation helpful? Give feedback.
All reactions