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
Sometimes, submitting a mnemosyne trace is not successful. One of the most recent errors I see frequently in my log include the following error:
E, [2023-10-13T07:26:19.148936 #469930] ERROR -- : Error while submitting trace: Trying to send frame through a closed connection. Frame is [REDACTED]
/shared/bundle/ruby/3.2.0/gems/bunny-2.22.0/lib/bunny/session.rb:1166:in `block in send_frameset'
/shared/bundle/ruby/3.2.0/gems/bunny-2.22.0/lib/bunny/channel.rb:1531:in `synchronize'
/shared/bundle/ruby/3.2.0/gems/bunny-2.22.0/lib/bunny/channel.rb:1531:in `synchronize'
/shared/bundle/ruby/3.2.0/gems/bunny-2.22.0/lib/bunny/session.rb:1159:in `send_frameset'
/shared/bundle/ruby/3.2.0/gems/bunny-2.22.0/lib/bunny/channel.rb:639:in `basic_publish'
/shared/bundle/ruby/3.2.0/gems/bunny-2.22.0/lib/bunny/exchange.rb:141:in `publish'
/shared/bundle/ruby/3.2.0/gems/mnemosyne-ruby-1.16.0/lib/mnemosyne/client.rb:44:in `call'
/shared/bundle/ruby/3.2.0/gems/mnemosyne-ruby-1.16.0/lib/mnemosyne/instrumenter.rb:49:in `submit'
/shared/bundle/ruby/3.2.0/gems/mnemosyne-ruby-1.16.0/lib/mnemosyne/trace.rb:40:in `submit'
/shared/bundle/ruby/3.2.0/gems/mnemosyne-ruby-1.16.0/lib/mnemosyne/middleware/rack.rb:50:in `_submit_trace'
/shared/bundle/ruby/3.2.0/gems/mnemosyne-ruby-1.16.0/lib/mnemosyne/middleware/rack.rb:32:in `close'
/shared/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/request.rb:137:in `handle_request'
/shared/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/server.rb:443:in `process_client'
/shared/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/server.rb:241:in `block in run'
/shared/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/thread_pool.rb:155:in `block in spawn_thread'
E, [2023-10-13T07:35:25.557811 #475629] ERROR -- : Got an exception when sending data: IO timeout when writing to socket (Timeout::Error)
W, [2023-10-13T07:35:25.558779 #475629] WARN -- : Will recover from a network failure (no retry limit)...
W, [2023-10-13T07:35:35.561585 #475629] WARN -- : Retrying connection on next host in line: REDACTED:5672
I would suggest to handle this exception more gracefully within mnemosyne.
The text was updated successfully, but these errors were encountered:
Sometimes, submitting a mnemosyne trace is not successful. One of the most recent errors I see frequently in my log include the following error:
I would suggest to handle this exception more gracefully within mnemosyne.
The text was updated successfully, but these errors were encountered: