[rabbitmq-discuss] Problems with RabbitMQ not responding on channel request
Cal Leeming [Simplicity Media Ltd]
cal.leeming at simplicitymedialtd.co.uk
Thu Aug 19 01:16:17 BST 2010
Hi all,
I am now getting the following errors when using RabbitMQ with Python Celery
and Django Celery..
The below error messages doesn't mean much to be sadly.. Could anyone shed
some light on what the below actually means??
Cheers
Cal
==> /var/log/rabbitmq/rabbit at mail01.log <==
=WARNING REPORT==== 19-Aug-2010::01:13:31 ===
exception on TCP connection <0.2829.0> from 10.1.3.1:54996
connection_closed_abruptly
=INFO REPORT==== 19-Aug-2010::01:13:31 ===
closing TCP connection <0.2829.0> from 10.1.3.1:54996
=INFO REPORT==== 19-Aug-2010::01:13:32 ===
accepted TCP connection on 0.0.0.0:5672 from 10.1.3.1:44483
=INFO REPORT==== 19-Aug-2010::01:13:32 ===
starting TCP connection <0.2923.0> from 10.1.3.1:44483
=INFO REPORT==== 19-Aug-2010::01:13:32 ===
accepted TCP connection on 0.0.0.0:5672 from 10.1.3.1:44484
=INFO REPORT==== 19-Aug-2010::01:13:32 ===
starting TCP connection <0.2925.0> from 10.1.3.1:44484
=ERROR REPORT==== 19-Aug-2010::01:13:32 ===
** Generic server <0.2936.0> terminating
** Last message in was {'$gen_cast',
{method,
{'basic.publish',0,<<"tasks">>,
<<"bluemail.cache.updatecampaignstatus">>,
false,false},
{content,60,none,
<<208,0,30,97,112,112,108,105,99,97,116,105,
111,110,47,120,45,112,121,116,104,111,110,
45,115,101,114,105,97,108,105,122,101,6,
98,105,110,97,114,121,2>>,
rabbit_framing_amqp_0_8,
[<<"(dp1\nS'retries'\np2\nI0\nsS'task'\np3\nS'webapp.bluemail.tasks.UpdateCampaignStatus'\np4\nsS'args'\np5\n(lp6\nsS'eta'\np7\nNsS'kwargs'\np8\n(dp9\nsS'id'\np10\nS'c49f1e35-a042-43ba-9316-3e99e27a6bf7'\np11\ns.">>]}}}
** When Server state == {ch,running,1,<0.2925.0>,<0.2934.0>,undefined,none,
{sets,0,16,16,8,80,48,
{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
[],[]},
{{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
[],[]}}},
1,
{[],[]},
{[],[]},
<<"simplicitymedialtd">>,<<"bluemail_dev">>,<<>>,
{dict,0,16,16,8,80,48,
{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
[],[]},
{{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
[],[]}}},
{dict,0,16,16,8,80,48,
{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
[],[]},
{{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
[],[]}}},
<0.2926.0>,
{state,none,undefined}}
** Reason for termination ==
** {{undef,[{re,split,
[<<"bluemail.cache.#">>,"\\.",[{return,list}]]},
{rabbit_exchange_type_topic,topic_matches,2},
{rabbit_router,'-match_bindings/2-fun-1-',10},
{qlc,collect,1},
{qlc,eval,2},
{mnesia_tm,non_transaction,5},
{rabbit_router,match_bindings,2},
{rabbit_exchange_type_topic,publish,2}]},
[{mnesia_tm,non_transaction,5},
{rabbit_router,match_bindings,2},
{rabbit_exchange_type_topic,publish,2},
{rabbit_exchange,publish,3},
{rabbit_channel,handle_method,3},
{rabbit_channel,handle_cast,2},
{gen_server2,handle_msg,7},
{proc_lib,init_p,5}]}
=ERROR REPORT==== 19-Aug-2010::01:13:32 ===
connection <0.2925.0> (running), channel 1 - error:
{{undef,[{re,split,
[<<"bluemail.cache.#">>,"\\.",[{return,list}]]},
{rabbit_exchange_type_topic,topic_matches,2},
{rabbit_router,'-match_bindings/2-fun-1-',10},
{qlc,collect,1},
{qlc,eval,2},
{mnesia_tm,non_transaction,5},
{rabbit_router,match_bindings,2},
{rabbit_exchange_type_topic,publish,2}]},
[{mnesia_tm,non_transaction,5},
{rabbit_router,match_bindings,2},
{rabbit_exchange_type_topic,publish,2},
{rabbit_exchange,publish,3},
{rabbit_channel,handle_method,3},
{rabbit_channel,handle_cast,2},
{gen_server2,handle_msg,7},
{proc_lib,init_p,5}]}
=WARNING REPORT==== 19-Aug-2010::01:13:32 ===
Non-AMQP exit reason '{{undef,[{re,split,
[<<"bluemail.cache.#">>,"\\.",
[{return,list}]]},
{rabbit_exchange_type_topic,topic_matches,2},
{rabbit_router,'-match_bindings/2-fun-1-',10},
{qlc,collect,1},
{qlc,eval,2},
{mnesia_tm,non_transaction,5},
{rabbit_router,match_bindings,2},
{rabbit_exchange_type_topic,publish,2}]},
[{mnesia_tm,non_transaction,5},
{rabbit_router,match_bindings,2},
{rabbit_exchange_type_topic,publish,2},
{rabbit_exchange,publish,3},
{rabbit_channel,handle_method,3},
{rabbit_channel,handle_cast,2},
{gen_server2,handle_msg,7},
{proc_lib,init_p,5}]}'
=INFO REPORT==== 19-Aug-2010::01:13:32 ===
closing TCP connection <0.2925.0> from 10.1.3.1:44484
==> /var/log/rabbitmq/rabbit at mail01-sasl.log <==
=CRASH REPORT==== 19-Aug-2010::01:13:32 ===
crasher:
pid: <0.2936.0>
registered_name: []
exception exit: {{undef,[{re,split,
[<<"bluemail.cache.#">>,"\\.",
[{return,list}]]},
{rabbit_exchange_type_topic,topic_matches,2},
{rabbit_router,'-match_bindings/2-fun-1-',10},
{qlc,collect,1},
{qlc,eval,2},
{mnesia_tm,non_transaction,5},
{rabbit_router,match_bindings,2},
{rabbit_exchange_type_topic,publish,2}]},
[{mnesia_tm,non_transaction,5},
{rabbit_router,match_bindings,2},
{rabbit_exchange_type_topic,publish,2},
{rabbit_exchange,publish,3},
{rabbit_channel,handle_method,3},
{rabbit_channel,handle_cast,2},
{gen_server2,handle_msg,7},
{proc_lib,init_p,5}]}
in function gen_server2:terminate/6
initial call: gen:init_it(gen_server2,<0.2935.0>,<0.2935.0>,
rabbit_channel,
[1,<0.2925.0>,<0.2934.0>,
<<"simplicitymedialtd">>,<<"bluemail_dev">>,
<0.2926.0>],
[])
ancestors: [<0.2935.0>]
messages: []
links: [<0.2935.0>]
dictionary: [{permission_cache,
[{{resource,<<"bluemail_dev">>,exchange,<<"tasks">>},
write},
{{resource,<<"bluemail_dev">>,exchange,<<"tasks">>},
configure}]},
{guid,{{0,<0.2936.0>},0}}]
trap_exit: true
status: running
heap_size: 610
stack_size: 23
reductions: 2649
neighbours:
==> /var/log/rabbitmq/rabbit at mail01.log <==
=INFO REPORT==== 19-Aug-2010::01:13:38 ===
closing TCP connection <0.2923.0> from 10.1.3.1:44483
^C
root at mail01.dmemedialtd.com [~/rabbitmq-server/scripts] >
On Wed, Aug 18, 2010 at 11:39 PM, Matthew Sackman <matthew at rabbitmq.com>wrote:
> Hi Cal,
>
> > On Wed, Aug 18, 2010 at 10:44 PM, Cal Leeming [Simplicity Media Ltd] <
> > cal.leeming at simplicitymedialtd.co.uk> wrote:
> > > This might be a little question but, if RabbitMQ runs out of memory,
> and I
> > > am unable to open a new channel, how would one then consume off the
> queue,
> > > if one isn't able to open a channel to do so? Or is this something
> which has
> > > been solved with the new persister?
>
> The "new persister" is the solution to this problem and has recently
> been merged into the default branch (a couple of weeks ago) which is why
> you're now seeing that this isn't so much of a problem.
>
> Basically, the "new persister" allows paging of messages so Rabbit
> should never run out of memory for very long - it should always (well,
> nearly always) be able to free up some memory by writing messages out to
> disk.
>
> Glad it's now working for you.
>
> Matthew
>
--
Cal Leeming
Operational Security & Support Team
*Out of Hours: *+44 (07534) 971120 | *Support Tickets: *
support at simplicitymedialtd.co.uk
*Fax: *+44 (02476) 578987 | *Email: *cal.leeming at simplicitymedialtd.co.uk
Simplicity Media Ltd. All rights reserved.
Registered company number 7143564
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100819/de6ac73a/attachment-0001.htm>
More information about the rabbitmq-discuss
mailing list