sunjam
(james.network)
30 Abril, 2022 15:58
1
Ayudando a @rakekniven a solucionar problemas de rendimiento del foro y los usuarios ya no pueden cargar imágenes. Este error ha estado apareciendo mucho. Parece que esta persona también está teniendo errores similares y tampoco puede cargar imágenes .
Plugins en el foro
Respuestas predefinidas
discourse-checklist
discourse-legal-tools
discourse-solved
docker_manager
styleguide - deshabilitado
Mensaje (661 copias reportadas) en 2.9.0.beta4
#<Net::OpenTimeout: execution expired>
Backtrace
/usr/local/lib/ruby/2.7.0/net/http.rb:960:in initialize' /usr/local/lib/ruby/2.7.0/net/http.rb:960:in open’
/usr/local/lib/ruby/2.7.0/net/http.rb:960:in block in connect' /usr/local/lib/ruby/2.7.0/timeout.rb:105:in timeout’
/usr/local/lib/ruby/2.7.0/net/http.rb:958:in connect' /usr/local/lib/ruby/2.7.0/net/http.rb:943:in do_start’
/usr/local/lib/ruby/2.7.0/net/http.rb:932:in start' /usr/local/lib/ruby/2.7.0/net/http.rb:606:in start’
/var/www/discourse/lib/final_destination.rb:515:in safe_session' /var/www/discourse/lib/final_destination.rb:455:in safe_get’
sunjam
(james.network)
30 Abril, 2022 20:37
3
Error de carga
Net::OpenTimeout : execution expired
Mensaje (273757 copias reportadas)
Error al procesar la respuesta secuestrada correctamente: Net::OpenTimeout : execution expired
Rastreo
/usr/local/lib/ruby/2.7.0/net/http.rb:960:in initialize' /usr/local/lib/ruby/2.7.0/net/http.rb:960:in open’
/usr/local/lib/ruby/2.7.0/net/http.rb:960:in block in connect' /usr/local/lib/ruby/2.7.0/timeout.rb:105:in timeout’
/usr/local/lib/ruby/2.7.0/net/http.rb:958:in connect' /usr/local/lib/ruby/2.7.0/net/http.rb:943:in do_start’
/usr/local/lib/ruby/2.7.0/net/http.rb:932:in start' /usr/local/lib/ruby/2.7.0/net/http.rb:606:in start’
/var/www/discourse/lib/final_destination.rb:515:in safe_session' /var/www/discourse/lib/final_destination.rb:455:in safe_get’
/var/www/discourse/lib/final_destination.rb:147:in get' /var/www/discourse/lib/file_helper.rb:68:in download’
/var/www/discourse/app/controllers/user_avatars_controller.rb:158:in proxy_avatar' /var/www/discourse/app/controllers/user_avatars_controller.rb:51:in block in show_proxy_letter’
/var/www/discourse/lib/hijack.rb:56:in instance_eval' /var/www/discourse/lib/hijack.rb:56:in block in hijack’
/var/www/discourse/lib/scheduler/defer.rb:94:in block in do_work' rails_multisite-4.0.1/lib/rails_multisite/connection_management.rb:80:in with_connection’
/var/www/discourse/lib/scheduler/defer.rb:89:in do_work' /var/www/discourse/lib/scheduler/defer.rb:79:in block (2 levels) in start_thread’
Entorno
sunjam
(james.network)
12 Mayo, 2022 16:05
4
Encontré esto en stackoverflow para resolver el problema en Ruby:
Parece ser un problema con ciertas versiones de libc que resuelven rutas DNS. Después de pasar un par de horas buscando una solución, solo necesitas agregar require 'resolv-replace' al principio de tu código.
Más información: Use Ruby DNS resolver to handle DNS timeout in Net::HTTP by pranas · Pull Request #597 · ruby/ruby · GitHub
Espero que esto ayude a alguien en el futuro.