Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

strange crash report every 4 minutes #192

Open
konstantino opened this issue Dec 6, 2013 · 2 comments
Open

strange crash report every 4 minutes #192

konstantino opened this issue Dec 6, 2013 · 2 comments

Comments

@konstantino
Copy link
Contributor

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?

@nikokon
Copy link
Contributor

nikokon commented Dec 6, 2013

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!)

@konstantino
Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants