TimeOut S3 bucket us-west-2

0

hi, one of your hops (62.115.136.82) between me and twelve99 seems to drop lots of packets. Are you aware of an ongoing incident and could you link me to a status page, please? or any solution?

This issue happens intermittently: Error: "Net::OpenTimeout: execution expired" Enter image description here

thanks

asked 2 months ago57 views
3 Answers
0
Accepted Answer

Hello,

Thanks for sharing the details, to troubleshoot the issue further. I request you to open a support case so that we can look into account specific details and assist you further.

SUPPORT ENGINEER
Rohan_S
answered 2 months ago
0

Hello,

Greetings of the day!

I checked and found that there is no incident reported for region US-WEST-2, also I reviewed the MTR output. I see that there is a packet loss of 86% only on 4th hop, but I would like to mention that a single spike doesn’t conclude any problem as long as the subsequent hops shows 0.0% Also we can see that the loss percentage is 0% for subsequent hops.

Please refer the following third party document for more information :

https://www.exavault.com/blog/reading-mtr-output

https://www.pingman.com/kb/24

I also researched about the error "Net::OpenTimeout:" you are getting and found that "Net::OpenTimeout is raised when a connection cannot be created within a specified amount of time. Getting this error a few times isn't always out of the ordinary, but you may want to add some error handling." Hence I request you to add error handling.

Please refer the third party document for more information :

https://www.exceptionalcreatures.com/bestiary/Net/OpenTimeout.html

NOTE : Providing the above link is for your reference only, however please note that third party links shared contain information which is not endorsed by AWS. Please test it on a demo environment before using in a production setup

Additionally, if the issue still persists, I request you to open a support case for further troubleshooting.

SUPPORT ENGINEER
Rohan_S
answered 2 months ago
0

Hi Rohan,

Thanks for the prompt response, I'll tell you a bit of context about our application:

The app has been deployed in a production environment for more than 4 years, it is created in ruby ​​with Amazon S3 to save files (images, pdf, xml, among others). Since September 15, 2022 our clients began to occasionally experience TimeOut errors, this has been increasing to date. when applying the mentioned https://stackoverflow.com/questions/42036133/ruby-netopentimeout-execution-expired we get the same timeout result in some requests.

For example a code that downloads an image, gets 5 timeouts out of 1297 requests

require 'resolv-replace'
companies = Company.where(active:true)
count = companies.count
images = []
companies.each do |company|
  begin
  unless company.logo.url.nil?
    path_logo = ENV['DIR_TMP_LOGO_FILE']
    filename = company.logo.file.filename
    filesystem_path = path_logo + "#{company.id}_default_#{filename}"
    
    File.delete(filesystem_path) if File.exist?(filesystem_path)
    File.open(filesystem_path, "wb") do |f|
      f.write(open(filesystem_path).read)
    end
  end
  rescue Exception => e
    images << [company.id, "ERROR", e]
  end
end
images.count
images

Output:

> 1297
> 5
> [[15221, "ERROR", #<Net::OpenTimeout: execution expired>], [4123, "ERROR", #<Net::OpenTimeout: execution expired>], [13218, "ERROR", #<Net::OpenTimeout: execution expired>], [12691, "ERROR", #<Net::OpenTimeout: execution expired>], [11764, "ERROR", #<Net::OpenTimeout: execution expired>]] 
answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions