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
I've been seeing this crash report occurring pretty much on a regular basis.
=ERROR REPORT==== 2-Dec-2013::14:31:09 ===
** Generic server <0.2011.0> terminating
** Last message in was {inet_async,#Port<0.4064>,6428,{ok,<<0,10,0,51,206>>}}
** When Server state == {state,#Port<0.4064>,<0.2006.0>,<0.2008.0>,
{method,rabbit_framing_amqp_0_9_1},
none}
** Reason for termination ==
** {socket_error,einval}
Thanks for pointing this out! I will look in to it! (sorry for sounding like a generic answer, just want you to know that we have noted the issue and that we are on the case!)
no worries "answering machine" :) just joking here
say you should be able to pick up this error somewhere in the logs, assuming you have a long-running version of the engine where someone is pushing data very frequently (i.e. per second). the error does not really cause anything - at least not to my understanding but maybe it's good to keep in the radar since it may have sideffects
hi,
I've been seeing this crash report occurring pretty much on a regular basis.
=ERROR REPORT==== 2-Dec-2013::14:31:09 ===
** Generic server <0.2011.0> terminating
** Last message in was {inet_async,#Port<0.4064>,6428,{ok,<<0,10,0,51,206>>}}
** When Server state == {state,#Port<0.4064>,<0.2006.0>,<0.2008.0>,
{method,rabbit_framing_amqp_0_9_1},
none}
** Reason for termination ==
** {socket_error,einval}
=CRASH REPORT==== 2-Dec-2013::14:31:09 ===
crasher:
initial call: amqp_main_reader:init/1
pid: <0.2011.0>
registered_name: []
exception exit: {socket_error,einval}
in functiongen_server:terminate/6 (gen_server.erl, line 744)
ancestors: [<0.2009.0>,<0.2005.0>,amqp_sup,<0.122.0>]
messages: []
links: []
dictionary: []
trap_exit: false
status: running
heap_size: 610
stack_size: 27
reductions: 752
neighbours:
Is this happening on your side too?
The text was updated successfully, but these errors were encountered: