[rabbitmq-discuss] Node crash

Emile Joubert emile at rabbitmq.com
Tue Aug 6 11:37:57 BST 2013

Hi Carl,

On 06/08/13 08:15, carlhoerberg wrote:
> Had a node crash in a cluster (due to memory exhaustion). When clients then
> reconnected to a healthy node, bind commands failed to return. And when the
> crashed node was restarted the logs was flooded with: 
> =ERROR REPORT==== 5-Aug-2013::23:45:50 ===
> Discarding message
> {'$gen_call',{<0.7975.0>,#Ref<>},{deliver,{delivery,true,<5068.31152.5031>,{basic_message,{resource,<<8
> bytes>>,exchange,<<16 bytes>>},[<<7 bytes>>],{content,60,{'P_basic',<<24
> bytes>>,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined},<<27
> bytes>>,rabbit_framing_amqp_0_9_1,[<<299 bytes>>]},<<16
> bytes>>,false},396},true}} from <0.7975.0> to <0.26389.5794> in an old
> incarnation (3) of this node (1)
> The only solution was to restart all nodes in the cluster. 

One or two of these messages (Discarding message ... in an old
incarnation) does not indicate an error condition, and can safely be

If you see large numbers of these messages then that does indicate a
problem. A cause has been identified and fixed since 3.1.3. The release
notes containing the fix will contain the tag "25670". You should
upgrade when this release becomes available.

(You can obtain the fix sooner by building from source, making sure to
use the "stable" branch: http://www.rabbitmq.com/build-server.html)


More information about the rabbitmq-discuss mailing list