Has anyone had any more thoughts on this? I'm still getting this error and it's making my software queue up about 10 for every 100,000 messages in the unacked queue. If I restart my server it will process those messages just fine.<br>
-Max<br><br><div class="gmail_quote">On Thu, Aug 18, 2011 at 4:26 PM, Max Warnock <span dir="ltr"><<a href="mailto:maxjwarnock@gmail.com">maxjwarnock@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I have been getting the same error, you're not crazy Chak. The exact message for me is:<div><br></div><div><div><div>=ERROR REPORT==== 18-Aug-2011::16:17:35 ===</div><div>** Generic server <0.28256.0> terminating </div>
<div>** Last message in was {inet_async,#Port<0.29961>,47384,</div><div> {ok,<<0,10,0,51,206>>}}</div><div>** When Server state == {state,#Port<0.29961>,<0.28252.0>,<0.28253.0>,</div>
<div class="im">
<div> {method,rabbit_framing_amqp_0_9_1},</div><div> {1,0,4}}</div><div>** Reason for termination == </div><div>** {{badmatch,{error,einval}},</div><div> [{amqp_main_reader,handle_inet_async,2},</div>
<div> {gen_server,handle_msg,5},</div><div> {proc_lib,init_p_do_apply,3}]}</div></div></div><div><br></div><div>I get this when I have a large number of messages going over a single connection and channel (topic exchange, subscription based pulling). I'm running</div>
<div>Erlang R13B04 (erts-5.7.5).</div><div><br></div><div>Regards,</div><div>-Max</div><div><div></div><div class="h5"><div><br></div><br><div class="gmail_quote">On Wed, Jul 27, 2011 at 12:38 PM, Alexandru Scvorţov <span dir="ltr"><<a href="mailto:alexandru@rabbitmq.com" target="_blank">alexandru@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Chak,<br>
<br>
I've been trying for a while, but I can't reproduce this.<br>
<br>
That error is coming from deep inside Erlang's inet driver. As far as I<br>
can tell, the only way to get that error would be to call<br>
prim_inet:async_recv/3 on a socket with a {packet, Packet} setting<br>
different from 'raw'. But this can't happen on any version of rabbit.<br>
<br>
Could you give us a more detailed description of the program? Is it a<br>
plugin? Is it doing anything special with the connection? (like setting<br>
socket options after the connection is established) Is there any chance<br>
we could see the code?<br>
<br>
You mentioned it starts at the very beginning. Does this mean the<br>
problem goes away after some time?<br>
<br>
Cheers,<br>
Alex<br>
<div><div></div><div><br>
<br>
On Thu, Jul 21, 2011 at 07:48:29PM -0700, Chak Hedik wrote:<br>
> Hi Alex,<br>
><br>
> Seems like this error is still there and it seems like either it<br>
> occurred when worker entering the loop and send another message to the<br>
> same queue within the loop or occurred when function retry, means<br>
> function call itself for a retry (pretty much like loop also).<br>
><br>
> Thanks,<br>
> Chak<br>
><br>
> On Jul 21, 6:40 am, Chak Hedik <<a href="mailto:chakhe...@gmail.com" target="_blank">chakhe...@gmail.com</a>> wrote:<br>
> > Hi Alex,<br>
> ><br>
> > *Ubuntu Server 11.04 64-Bit<br>
> > *RabbitMQ 2.3.1 (Default ubuntu package)<br>
> > *Erlang Client 2.3.1 (Default ubuntu package)<br>
> > *Erlang R13B03 (Default ubuntu package)<br>
> ><br>
> > Is there something in the server logs that corresponds to this error?<br>
> > - That's the only thing appeared in the logs.<br>
> ><br>
> > You say your other nodes don't have similar issues. Is there<br>
> > something<br>
> > special about this node?<br>
> > - Nothing special, pretty much the same but handle more messages than<br>
> > others. 1 worker handling 1 queue.<br>
> ><br>
> > It is strange behaviour and it happen at the very beginning where the<br>
> > worker up for the first time (no message in queue yet). I've created<br>
> > another node and put this worker there and will wait and see if<br>
> > similar error appear again or not today.<br>
> ><br>
> > Thanks for your reply.<br>
> ><br>
> > Chak<br>
> ><br>
> > On Jul 21, 5:14 am, Alexandru Scvorţov <<a href="mailto:alexan...@rabbitmq.com" target="_blank">alexan...@rabbitmq.com</a>> wrote:<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > > Hi Chak,<br>
> ><br>
> > > Could you please answer the following questions:<br>
> > > * What OS are you using?<br>
> > > * What version of RabbitMQ?<br>
> > > * What version of the Erlang client?<br>
> > > * What version of Erlang?<br>
> ><br>
> > > > ** Reason for termination ==<br>
> > > > ** {{badmatch,{error,einval}},<br>
> > > > [{amqp_main_reader,handle_inet_async,2},<br>
> > > > {gen_server,handle_msg,5},<br>
> > > > {proc_lib,init_p_do_apply,3}]}<br>
> ><br>
> > > Looks like something strange is taking down the socket, which in turn is<br>
> > > taking down the entire connection. If you have more than one<br>
> > > connection, the others should be fine.<br>
> ><br>
> > > Is there something in the server logs that corresponds to this error?<br>
> ><br>
> > > You say your other nodes don't have similar issues. Is there something<br>
> > > special about this node?<br>
> ><br>
> > > Cheers,<br>
> > > Alex<br>
> ><br>
> > > On Wed, Jul 20, 2011 at 12:12:32AM -0700, Chak Hedik wrote:<br>
> > > > Hi,<br>
> ><br>
> > > > I frequently getting this terminating error from one of my nodes :<br>
> ><br>
> > > > ** Generic server <0.28067.2> terminating<br>
> > > > ** Last message in was {inet_async,#Port<0.15349>,9049,<br>
> > > > {ok,<<0,10,0,51,206>>}}<br>
> > > > ** When Server state == {state,#Port<0.15349>,<0.28063.2>,<0.28064.2>,<br>
> > > > {method,rabbit_framing_amqp_0_9_1},<br>
> > > > {1,0,4}}<br>
> > > > ** Reason for termination ==<br>
> > > > ** {{badmatch,{error,einval}},<br>
> > > > [{amqp_main_reader,handle_inet_async,2},<br>
> > > > {gen_server,handle_msg,5},<br>
> > > > {proc_lib,init_p_do_apply,3}]}<br>
> ><br>
> > > > While several other nodes with the same setup didn't have the same<br>
> > > > issue. May I know what it means and willl it affect my queues?How do I<br>
> > > > fix this?<br>
> ><br>
> > > > Thank,<br>
> > > > Chak<br>
> > > > _______________________________________________<br>
> > > > rabbitmq-discuss mailing list<br>
> > > > <a href="mailto:rabbitmq-disc...@lists.rabbitmq.com" target="_blank">rabbitmq-disc...@lists.rabbitmq.com</a><br>
> > > ><a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
> ><br>
> > > _______________________________________________<br>
> > > rabbitmq-discuss mailing list<br>
> > > rabbitmq-disc...@lists.rabbitmq.comhttps://<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
> ><br>
> > _______________________________________________<br>
> > rabbitmq-discuss mailing list<br>
> > rabbitmq-disc...@lists.rabbitmq.comhttps://<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br>