No subject
Thu Feb 16 03:44:05 GMT 2012
explicitly specified
--047d7b33d9bef7fea004be9d55ad
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_extra">Hi Matthew,<br><br>Thanks for your reply. At lea=
st web UI reports that all 3 nodes are 2.8.1 so I guess they are=A0 up to d=
ate.<br>Reproducing this bug is difficult. I'll work on it for may be 2=
more days, trying to find a combination which would be reproducible. Very =
preliminary, I have impression that "exclusive" queue flag have s=
omething to do with it, but I will experiment with ttl too, as you suggeste=
d. <br>
<br>I dont know if it is related, but I had a strange situation when there =
was an exclusive autodelete queue without a connection (connection reported=
"unknown") and it was impossible to delete it because "reso=
urce lock" error. <br>
Hopefully I'll be able to report more tomorrow.<br><br>Thanks,<br>Vadim=
.<br><br><div class=3D"gmail_quote">On Thu, Apr 26, 2012 at 3:31 PM, Matthe=
w Sackman <span dir=3D"ltr"><<a href=3D"mailto:matthew at rabbitmq.com" tar=
get=3D"_blank">matthew at rabbitmq.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Vadim,<br>
<div class=3D"im"><br>
On Thu, Apr 26, 2012 at 01:01:20PM -0700, Vadim Chekan wrote:<br>
> I'm testing my active-active setup (2.8.1, linux 64) and I am rand=
omly<br>
> running into some crashes when I'm stopping a node. I can stop one=
node<br>
> abut another one fails along with it. Below is a crash log.<br>
><br>
</div><div class=3D"im">> =3DERROR REPORT=3D=3D=3D=3D 26-Apr-2012::12:15=
:59 =3D=3D=3D<br>
> Discarding message<br>
> {'$gen_call',{<0.1955.0>,#Ref<0.0.0.5513>},{add_on=
_right,{9,<0.1955.0>}}}<br>
> from <0.1955.0> to <0.26823.834><br>
> =A0in an old incarnation (2) of this node (3)<br>
<br>
</div>I'm worried about these messages. Someone else on this list has s=
een<br>
this sort of thing too and it's causing them trouble. I've not seen=
this<br>
issue myself in testing which is frustrating. However, that's not the<b=
r>
cause of your crash in this case (I think).<br>
<div class=3D"im"><br>
> ** Generic server <0.1800.0> terminating<br>
> ** Last message in was {'$gen_cast',{gm_deaths,[<0.4684.0&g=
t;]}}<br>
> ** When Server state =3D=3D {state,<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {amqqueue,<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {resou=
rce,<<"/">>,queue,<<"test_29">>=
},<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 true,f=
alse,<0.1433.0>,<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [{<=
<"x-ha-policy">>,longstr,<<"all">>=
},<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0{&l=
t;<"x-message-ttl">>,signedint,600000}],<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <0.=
1799.0>,[],all},<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <0.1801.0&g=
t;,<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {dict,0,16,16,=
8,80,48,<br>
><br>
> {[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0[]}=
,<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {{[],[=
],[],[],[],[],[],[],[],[],[],[],[],[],<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 []=
,[]}}},<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 #Fun<rabbit=
_mirror_queue_master.1.2951048>,<br>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 #Fun<rabbit=
_mirror_queue_master.2.72654940>}<br>
> ** Reason for termination =3D=3D<br>
> ** {{case_clause,{ok,<3066.9234.0>,[<0.4683.0>]}},<br>
> =A0 =A0 [{rabbit_mirror_queue_coordinator,handle_cast,2},<br>
> =A0 =A0 =A0{gen_server2,handle_msg,2},<br>
> =A0 =A0 =A0{proc_lib,wake_up,3}]}<br>
<br>
</div>Well this is very odd. We fixed a bug that looked like this, but it g=
ot<br>
fixed in 2.7.1 (and related to x-ha-policy =3D nodes. Could you just check<=
br>
that you really are running 2.8.1? We're not aware of any bug in this<b=
r>
area in 2.8.1, but that's certainly not saying there's not one ther=
e! Is<br>
there any particular sequence of events that you can perform that<br>
reliably triggers this crash? Could you also check the logs of the other<br=
>
nodes (both .log and -sasl.log) to see if there's further crash reports=
<br>
in there?<br>
<br>
Also, there have been discovered lots of bugs relating to the code<br>
changes made to add DLX support in 2.8.1, especially in relation to HA.<br>
It's possible one of the issues I found with TTL and HA is causing this=
.<br>
2.8.2 should be out soonish which might introduce fewer new bugs than it<br=
>
fixes, but in the mean time, could you try without the TTL and see if<br>
that helps?<br>
<br>
Matthew<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href=3D"mailto:rabbitmq-discuss at lists.rabbitmq.com">rabbitmq-discuss at lis=
ts.rabbitmq.com</a><br>
<a href=3D"https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-dis=
cuss" target=3D"_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo=
/rabbitmq-discuss</a><br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>From RFC 2631: In ASN.1=
, EXPLICIT tagging is implicit unless IMPLICIT is explicitly specified<br>
</div>
--047d7b33d9bef7fea004be9d55ad--
More information about the rabbitmq-discuss
mailing list