RabbitMQ cluster crash with stuck queues (RabbitMQ 3.6.9, Erlang 19.3)

6,840 views
Skip to first unread message

Aneci Adrian

unread,
Apr 27, 2017, 5:28:05 AM4/27/17
to rabbitmq-users
Hi team,

We have some issues in a 2-nodes rabbitmq cluster. After a master node restart some of the queues got stuck being unresponsive(NaN value in UI and no ha policy applied on them).
Also we cannot delete them from the UI, the browser freeze after delete button is pressed.
From the logs I've found a lot of errors after the master started up.
Below you can find some snipped logs:

=ERROR REPORT==== 19-Apr-2017::09:21:28 ===
** Generic server <0.919.0> terminating
** Last message in was {'$gen_cast',go}
** When Server state == {not_started,
                            {amqqueue,
                                {resource,<<"sensu">>,queue,
                                    <<"QUEUE_NAME">>},
                                false,true,none,[],<7225.2872.0>,[],[],
                                ['rabbit@node-1'],
                                [{vhost,<<"sensu">>},
                                 {name,<<"hapolicy">>},
                                 {pattern,<<"^.">>},
                                 {'apply-to',<<"all">>},
                                 {definition,
                                     [{<<"ha-mode">>,<<"all">>},
                                      {<<"ha-sync-mode">>,<<"automatic">>}]},
                                 {priority,0}],
                                [{<7225.2873.0>,<7225.2872.0>}],
                                [],live,0}}
** Reason for termination == 
** {noproc,
       {gen_server2,call,
           [msg_store_transient,
            {new_client_state,
                <<74,182,53,1,204,63,175,161,65,87,1,84,46,29,215,150>>,
                <0.919.0>,undefined,#Fun<rabbit_variable_queue.20.118228399>},
            infinity]}}


=ERROR REPORT==== 19-Apr-2017::09:43:04 ===
Discarding message {'$gen_call',{<0.16596.1>,#Ref<0.0.2.48068>},stat} from <0.16596.1> to <0.6006.0> in an old incarnation (1) of this node (3)

=ERROR REPORT==== 26-Apr-2017::05:47:38 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.3095>},stat} from <0.11897.0> to <0.499.0> in an old incarnation (1) of this node (3)

=WARNING REPORT==== 26-Apr-2017::05:47:38 ===
msg_store_persistent: rebuilding indices from scratch

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2687.5> (10.104.100.242:51852 -> 172.18.0.2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'QUEUE_NAME' in vhost 'sensu' due to timeout

Can you please give us a hist what can be the problem? Can be a bug?
Thank you!

Regards,
Adrian.

Karl Nilsson

unread,
Apr 27, 2017, 6:23:50 AM4/27/17
to rabbitm...@googlegroups.com
Hi,

It looks like the message store might have gone down and restarted. Could you share a more complete log from both nodes and the steps you have already taken to try to resolve it?

Cheers
Karl

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Karl Nilsson

Pivotal/RabbitMQ

Aneci Adrian

unread,
Apr 27, 2017, 8:34:55 AM4/27/17
to rabbitmq-users
Hi Karl,

Here are some detailed logs form the node that was restarted and also the one that use to be the master:

{code}
=INFO REPORT==== 26-Apr-2017::05:47:31 ===
Starting RabbitMQ 3.6.9 on Erlang 19.3
Copyright (C) 2007-2016 Pivotal Software, Inc.
Licensed under the MPL.  See http://www.rabbitmq.com/

=INFO REPORT==== 26-Apr-2017::05:47:31 ===
node           : rabbit@sensu-prod-rabbit-1
home dir       : /var/lib/rabbitmq
config file(s) : /etc/rabbitmq/rabbitmq.config
cookie hash    : kwA70MfN15Db51BmexXZQg==
log            : /data/rabbitmq_sensu-prod-rabbit-1.log
sasl log       : tty
database dir   : /data/mnesia

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Memory limit set to 12702MB of 31756MB total.

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Disk free limit set to 50MB

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Limiting to approx 65436 file handles (58890 sockets)

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
FHC read buffering:  OFF
FHC write buffering: ON

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Waiting for Mnesia tables for 30000 ms, 9 retries left

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Waiting for Mnesia tables for 30000 ms, 9 retries left

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Waiting for Mnesia tables for 30000 ms, 9 retries left

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Priority queues enabled, real BQ is rabbit_variable_queue

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Starting rabbit_node_monitor

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Management plugin: using rates mode 'basic'

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
msg_store_transient: using rabbit_msg_store_ets_index to provide index

=ERROR REPORT==== 26-Apr-2017::05:47:38 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.3095>},stat} from <0.11897.0> to <0.499.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:47:38 ===
msg_store_persistent: using rabbit_msg_store_ets_index to provide index

=WARNING REPORT==== 26-Apr-2017::05:47:38 ===
msg_store_persistent: rebuilding indices from scratch

=ERROR REPORT==== 26-Apr-2017::05:47:38 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.3108>},stat} from <0.11897.0> to <0.638.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Mirrored queue 'QUEUE_NAME' in vhost 'sensu': Adding mirror on node 'rabbit@sensu-prod-rabbit-1': <0.11982.0>

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Mirrored queue 'QUEUE_NAME' in vhost 'sensu': Adding mirror on node 'rabbit@sensu-prod-rabbit-1': <0.11986.0>

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Adding mirror on node 'rabbit@sensu-prod-rabbit-1': <0.11990.0>

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Mirrored queue 'QUEUE_NAME' in vhost 'sensu': Adding mirror on node 'rabbit@sensu-prod-rabbit-1': <0.11994.0>

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Mirrored queue 'QUEUE_NAME' in vhost 'sensu': Adding mirror on node 'rabbit@sensu-prod-rabbit-1': <0.11997.0>

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Adding mirror on node 'rabbit@sensu-prod-rabbit-1': <0.12002.0>

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Adding mirror on node 'rabbit@sensu-prod-rabbit-1': <0.12006.0>

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
Mirrored queue 'results' in vhost 'sensu': Adding mirror on node 'rabbit@sensu-prod-rabbit-1': <0.12010.0>

=ERROR REPORT==== 26-Apr-2017::05:47:38 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.3197>},stat} from <0.11897.0> to <0.403.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:47:38 ===
started TCP Listener on [::]:5672

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
rabbit on node 'rabbit@sensu-prod-rabbit-2' up

=ERROR REPORT==== 26-Apr-2017::05:47:38 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.3333>},stat} from <0.11897.0> to <0.387.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Management plugin started. Port: 15672

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Statistics database started.

=ERROR REPORT==== 26-Apr-2017::05:47:40 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.3991>},stat} from <0.11897.0> to <0.455.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Server startup complete; 6 plugins started.
 * rabbitmq_management
 * rabbitmq_web_dispatch
 * rabbitmq_management_agent
 * cowboy
 * cowlib
 * amqp_client

=ERROR REPORT==== 26-Apr-2017::05:47:40 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.1.7615>},stat} from <0.11897.0> to <0.751.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.2674.5> (ip1:51846 -> ip2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.2674.5> (ip1:51846 -> ip2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.1.151430>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.2687.5> (IP1:51852 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.2687.5> (IP1:51852 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.1.151467>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.2699.5> (IP1:51858 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.2699.5> (IP1:51858 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.1.151504>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.2713.5> (IP1:51862 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.2713.5> (IP1:51862 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.1.151541>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.2724.5> (IP1:51868 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.103276>},stat} from <0.11897.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.2724.5> (ip1:51868 -> ip2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103285>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.2737.5> (IP1:51872 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.2737.5> (ip1:51872 -> ip2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.103291>},stat} from <0.11897.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.2750.5> (ip1:51876 -> ip2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.2753.5> (ip1:51880 -> ip2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.2750.5> (ip1:51876 -> ip2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.2753.5> (ip1:51880 -> ip2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.2772.5> (ip1:51884 -> ip2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.2772.5> (ip1:51884 -> ip2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103311>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.2785.5> (IP1:51890 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.2785.5> (ip1:51890 -> ip2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103324>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2796.5> (ip1:51894 -> ip2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.103328>},stat} from <0.11897.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2800.5> (ip1:51898 -> ip2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2796.5> (ip1:51894 -> ip2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2800.5> (ip1:51898 -> ip2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2820.5> (ip1:51902 -> ip2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2823.5> (IP1:51906 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103348>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2820.5> (IP1:51902 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2823.5> (IP1:51906 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.103374>},stat} from <0.11897.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2843.5> (IP1:51910 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2847.5> (IP1:51914 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2850.5> (IP1:51918 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2847.5> (IP1:51914 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2856.5> (IP1:51922 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2850.5> (IP1:51918 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2856.5> (IP1:51922 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2878.5> (IP1:51926 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2843.5> (IP1:51910 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2878.5> (IP1:51926 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2895.5> (IP1:51930 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2895.5> (IP1:51930 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2906.5> (IP1:51934 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103490>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2913.5> (IP1:51938 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2913.5> (IP1:51938 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.103512>},stat} from <0.11897.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2906.5> (IP1:51934 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2929.5> (IP1:51942 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2932.5> (IP1:51946 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2940.5> (IP1:51950 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2929.5> (IP1:51942 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2947.5> (IP1:51954 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2951.5> (IP1:51958 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2932.5> (IP1:51946 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2961.5> (IP1:51962 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2940.5> (IP1:51950 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.2968.5> (IP1:51966 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2961.5> (IP1:51962 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2968.5> (IP1:51966 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103646>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2947.5> (IP1:51954 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.2951.5> (IP1:51958 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3003.5> (IP1:51970 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3006.5> (IP1:51974 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.103674>},stat} from <0.11897.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3006.5> (IP1:51974 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3003.5> (IP1:51970 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3031.5> (IP1:51978 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3034.5> (IP1:51982 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3031.5> (IP1:51978 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3034.5> (IP1:51982 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3049.5> (IP1:51986 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3049.5> (IP1:51986 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3068.5> (IP1:51990 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3068.5> (IP1:51990 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103776>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3081.5> (IP1:51994 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3081.5> (IP1:51994 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103791>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3093.5> (IP1:51998 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3093.5> (IP1:51998 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3105.5> (IP1:52002 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3105.5> (IP1:52002 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103823>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3120.5> (IP1:52010 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3120.5> (IP1:52010 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3132.5> (IP1:52014 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103864>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3132.5> (IP1:52014 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3145.5> (IP1:52018 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103895>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3145.5> (IP1:52018 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.103904>},stat} from <0.11897.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3158.5> (IP1:52022 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3158.5> (IP1:52022 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3169.5> (IP1:52026 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103955>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3169.5> (IP1:52026 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.103965>},stat} from <0.11897.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3181.5> (IP1:52030 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11921.0>,#Ref<0.0.2.103985>},stat} from <0.11921.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.3185.5> (IP1:52034 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3185.5> (IP1:52034 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_cast',{deliver,{delivery,false,false,<0.2682.5>,{basic_message,{resource,<<"sensu">>,exchange,<<"keepalives">>},[<<>>],{content,60,{'P_basic',<<"application/octet-stream">>,undefined,undefined,1,0,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined},<<152,0,24,97,112,112,108,105,99,97,116,105,111,110,47,111,99,116,101,116,45,115,116,114,101,97,109,1,0>>,rabbit_framing_amqp_0_9_1,[<<"{\"name\":\"SERVER\",\"address\":\"IP\",\"subscriptions\":[\"prod\",\"ams01\",\"SERVER\",\"client:SERVER\"],\"safe_mode\":false,\"keepalive\":{},\"socket\":{\"bind\":\"127.0.0.1\",\"port\":3030},\"version\":\"0.26.5\",\"timestamp\":1493185759}">>]},<<156,71,103,183,190,97,206,41,79,2,221,90,69,198,161,100>>,false},undefined,flow},false}} from <0.2682.5> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.3181.5> (IP1:52030 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:19 ===
Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.104028>},stat} from <0.11897.0> to <0.631.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:21 ===
accepting AMQP connection <0.4328.5> (IP1:52050 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:21 ===
Discarding message {'$gen_call',{<0.2980.5>,#Ref<0.0.1.153824>},stat} from <0.2980.5> to <0.547.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:22 ===
connection <0.4328.5> (IP1:52050 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:22 ===
Discarding message {'$gen_call',{<0.3011.5>,#Ref<0.0.1.154440>},stat} from <0.3011.5> to <0.439.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:27 ===
accepting AMQP connection <0.3116.5> (IP1:52006 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:27 ===
Discarding message {'$gen_call',{<0.11910.0>,#Ref<0.0.4.20437>},stat} from <0.11910.0> to <0.719.0> in an old incarnation (1) of this node (3)


=WARNING REPORT==== 26-Apr-2017::05:49:27 ===
closing AMQP connection <0.3116.5> (IP1:52006 -> IP2:5672):
client unexpectedly closed TCP connection

=INFO REPORT==== 26-Apr-2017::05:49:28 ===
accepting AMQP connection <0.10304.5> (IP1:52122 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:28 ===
Discarding message {'$gen_call',{<0.3023.5>,#Ref<0.0.3.61146>},stat} from <0.3023.5> to <0.626.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:28 ===
connection <0.10304.5> (IP1:52122 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:28 ===
Discarding message {'$gen_call',{<0.3202.5>,#Ref<0.0.1.160012>},stat} from <0.3202.5> to <0.383.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:43 ===
accepting AMQP connection <0.22055.5> (IP1:52284 -> IP2:5672)

=ERROR REPORT==== 26-Apr-2017::05:49:43 ===
Discarding message {'$gen_call',{<0.2708.5>,#Ref<0.0.3.70321>},stat} from <0.2708.5> to <0.619.0> in an old incarnation (1) of this node (3)


=INFO REPORT==== 26-Apr-2017::05:49:43 ===
connection <0.22055.5> (IP1:52284 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:43 ===
Discarding message {'$gen_call',{<0.2922.5>,#Ref<0.0.2.122628>},stat} from <0.2922.5> to <0.667.0> in an old incarnation (1) of this node (3)


=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2674.5> (IP1:51846 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2674.5> (IP1:51846 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2687.5> (IP1:51852 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2687.5> (IP1:51852 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2699.5> (IP1:51858 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2699.5> (IP1:51858 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2724.5> (IP1:51868 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2724.5> (IP1:51868 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2750.5> (IP1:51876 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2750.5> (IP1:51876 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2713.5> (IP1:51862 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2713.5> (IP1:51862 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2753.5> (IP1:51880 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2753.5> (IP1:51880 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2737.5> (IP1:51872 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2737.5> (IP1:51872 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2847.5> (IP1:51914 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2796.5> (IP1:51894 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2847.5> (IP1:51914 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2772.5> (IP1:51884 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2796.5> (IP1:51894 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2772.5> (IP1:51884 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2800.5> (IP1:51898 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2823.5> (IP1:51906 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2800.5> (IP1:51898 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2823.5> (IP1:51906 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2850.5> (IP1:51918 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2878.5> (IP1:51926 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2878.5> (IP1:51926 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2850.5> (IP1:51918 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2940.5> (IP1:51950 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2820.5> (IP1:51902 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2856.5> (IP1:51922 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2785.5> (IP1:51890 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2820.5> (IP1:51902 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2856.5> (IP1:51922 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2940.5> (IP1:51950 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2785.5> (IP1:51890 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2895.5> (IP1:51930 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2895.5> (IP1:51930 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2913.5> (IP1:51938 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2913.5> (IP1:51938 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2843.5> (IP1:51910 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2843.5> (IP1:51910 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2968.5> (IP1:51966 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2968.5> (IP1:51966 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.3003.5> (IP1:51970 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2947.5> (IP1:51954 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.3003.5> (IP1:51970 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2951.5> (IP1:51958 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.2906.5> (IP1:51934 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2947.5> (IP1:51954 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2951.5> (IP1:51958 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:50:22 ===
Channel error on connection <0.3031.5> (IP1:51978 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:50:22 ===
closing AMQP connection <0.2906.5> (IP1:51934 -> IP2:5672):
client unexpectedly closed TCP connection
{code}


And also some logs from the second node(the slave one):
{code}
=WARNING REPORT==== 26-Apr-2017::05:45:24 ===
closing AMQP connection <0.4993.0> (IP1:33630 -> IP2:5672):
client unexpectedly closed TCP connection

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
rabbit on node 'rabbit@sensu-prod-rabbit-1' down

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
node 'rabbit@sensu-prod-rabbit-1' down: connection_closed

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Slave <rab...@sensu-prod-rabbit-2.2.403.0> saw deaths of mirrors <rab...@sensu-prod-rabbit-1.1.411.0>

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Promoting slave <rab...@sensu-prod-rabbit-2.2.403.0> to master

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Slave <rab...@sensu-prod-rabbit-2.2.603.0> saw deaths of mirrors <rab...@sensu-prod-rabbit-1.1.615.0>

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Promoting slave <rab...@sensu-prod-rabbit-2.2.603.0> to master

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'results' in vhost 'sensu': Slave <rab...@sensu-prod-rabbit-2.2.363.0> saw deaths of mirrors <rab...@sensu-prod-rabbit-1.1.375.0>

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'results' in vhost 'sensu': Promoting slave <rab...@sensu-prod-rabbit-2.2.363.0> to master

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'results' in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'results' in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'results' in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Slave <rab...@sensu-prod-rabbit-2.2.698.0> saw deaths of mirrors <rab...@sensu-prod-rabbit-1.1.711.0>

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Promoting slave <rab...@sensu-prod-rabbit-2.2.698.0> to master

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:45:30 ===
accepting AMQP connection <0.8213.0> (IP1:56026 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:45:30 ===
connection <0.8213.0> (IP1:56026 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:08 ===
accepting AMQP connection <0.8485.0> (IP1:48664 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:08 ===
accepting AMQP connection <0.8488.0> (IP1:48668 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:08 ===
accepting AMQP connection <0.8482.0> (IP1:48660 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:08 ===
connection <0.8485.0> (IP1:48664 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:08 ===
connection <0.8482.0> (IP1:48660 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:08 ===
connection <0.8488.0> (IP1:48668 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:08 ===
accepting AMQP connection <0.8544.0> (IP1:48670 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:08 ===
connection <0.8544.0> (IP1:48670 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9085.0> (IP1:48738 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9090.0> (IP1:48744 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9093.0> (IP1:48740 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9096.0> (IP1:48742 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9099.0> (IP1:48750 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9102.0> (IP1:48746 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9105.0> (IP1:48760 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9108.0> (IP1:48748 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9111.0> (IP1:48764 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9114.0> (IP1:48754 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9117.0> (IP1:48758 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9120.0> (IP1:48756 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9123.0> (IP1:48752 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9126.0> (IP1:48774 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9129.0> (IP1:48762 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9132.0> (IP1:48782 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9135.0> (IP1:48766 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9138.0> (IP1:48790 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9141.0> (IP1:48784 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9144.0> (IP1:48786 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9147.0> (IP1:48776 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9150.0> (IP1:48780 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9153.0> (IP1:48768 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9156.0> (IP1:48792 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9159.0> (IP1:48794 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9162.0> (IP1:48770 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9165.0> (IP1:48778 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9168.0> (IP1:48772 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9174.0> (IP1:48788 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9177.0> (IP1:48800 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9171.0> (IP1:48796 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9180.0> (IP1:48798 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9085.0> (IP1:48738 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9186.0> (IP1:48802 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9190.0> (IP1:48806 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9193.0> (IP1:48804 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9196.0> (IP1:48810 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9199.0> (IP1:48808 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9202.0> (IP1:48812 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9099.0> (IP1:48750 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9093.0> (IP1:48740 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9205.0> (IP1:48814 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9126.0> (IP1:48774 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9090.0> (IP1:48744 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9111.0> (IP1:48764 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9108.0> (IP1:48748 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9114.0> (IP1:48754 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9117.0> (IP1:48758 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9102.0> (IP1:48746 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9105.0> (IP1:48760 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9129.0> (IP1:48762 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9096.0> (IP1:48742 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9132.0> (IP1:48782 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9138.0> (IP1:48790 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9237.0> (IP1:48818 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9135.0> (IP1:48766 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9120.0> (IP1:48756 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9159.0> (IP1:48794 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9144.0> (IP1:48786 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9156.0> (IP1:48792 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9174.0> (IP1:48788 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9147.0> (IP1:48776 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9150.0> (IP1:48780 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9168.0> (IP1:48772 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9141.0> (IP1:48784 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9162.0> (IP1:48770 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9153.0> (IP1:48768 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9279.0> (IP1:48822 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9177.0> (IP1:48800 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9190.0> (IP1:48806 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9165.0> (IP1:48778 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9193.0> (IP1:48804 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9186.0> (IP1:48802 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9180.0> (IP1:48798 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9171.0> (IP1:48796 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9381.0> (IP1:48816 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9199.0> (IP1:48808 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9123.0> (IP1:48752 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9196.0> (IP1:48810 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9435.0> (IP1:48824 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9490.0> (IP1:48820 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9505.0> (IP1:48828 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9508.0> (IP1:48832 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9512.0> (IP1:48830 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9515.0> (IP1:48826 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9518.0> (IP1:48834 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9202.0> (IP1:48812 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9536.0> (IP1:48840 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9544.0> (IP1:48836 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9205.0> (IP1:48814 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9550.0> (IP1:48846 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9541.0> (IP1:48842 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9554.0> (IP1:48848 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9557.0> (IP1:48838 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9560.0> (IP1:48854 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9563.0> (IP1:48856 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9566.0> (IP1:48844 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9581.0> (IP1:48852 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9572.0> (IP1:48850 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9569.0> (IP1:48858 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9575.0> (IP1:48864 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9578.0> (IP1:48862 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9237.0> (IP1:48818 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9584.0> (IP1:48868 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9591.0> (IP1:48860 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9435.0> (IP1:48824 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9279.0> (IP1:48822 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9594.0> (IP1:48866 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9508.0> (IP1:48832 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9512.0> (IP1:48830 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9605.0> (IP1:48874 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9578.0> (IP1:48862 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9560.0> (IP1:48854 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9624.0> (IP1:48870 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9572.0> (IP1:48850 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9656.0> (IP1:48878 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9554.0> (IP1:48848 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9518.0> (IP1:48834 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9563.0> (IP1:48856 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9381.0> (IP1:48816 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9569.0> (IP1:48858 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9557.0> (IP1:48838 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9575.0> (IP1:48864 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9550.0> (IP1:48846 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9544.0> (IP1:48836 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9536.0> (IP1:48840 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9566.0> (IP1:48844 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9581.0> (IP1:48852 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9541.0> (IP1:48842 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9505.0> (IP1:48828 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9490.0> (IP1:48820 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9678.0> (IP1:48872 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9591.0> (IP1:48860 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9584.0> (IP1:48868 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9515.0> (IP1:48826 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9605.0> (IP1:48874 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9818.0> (IP1:48880 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9717.0> (IP1:48876 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9821.0> (IP1:48882 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9824.0> (IP1:48884 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9827.0> (IP1:48894 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9830.0> (IP1:48896 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9833.0> (IP1:48892 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9836.0> (IP1:48890 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9839.0> (IP1:48888 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9842.0> (IP1:48898 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9845.0> (IP1:48886 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9848.0> (IP1:48902 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9656.0> (IP1:48878 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9594.0> (IP1:48866 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9851.0> (IP1:48900 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9880.0> (IP1:48906 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9883.0> (IP1:48908 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9886.0> (IP1:48910 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9889.0> (IP1:48912 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9678.0> (IP1:48872 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9893.0> (IP1:48916 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9903.0> (IP1:48914 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9624.0> (IP1:48870 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9824.0> (IP1:48884 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9717.0> (IP1:48876 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9906.0> (IP1:48918 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
accepting AMQP connection <0.9929.0> (IP1:48904 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9833.0> (IP1:48892 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9836.0> (IP1:48890 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9830.0> (IP1:48896 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9845.0> (IP1:48886 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9818.0> (IP1:48880 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9839.0> (IP1:48888 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9827.0> (IP1:48894 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9842.0> (IP1:48898 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9848.0> (IP1:48902 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9821.0> (IP1:48882 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9880.0> (IP1:48906 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9893.0> (IP1:48916 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9903.0> (IP1:48914 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9886.0> (IP1:48910 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9883.0> (IP1:48908 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9929.0> (IP1:48904 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9906.0> (IP1:48918 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9851.0> (IP1:48900 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:14 ===
connection <0.9889.0> (IP1:48912 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:15 ===
accepting AMQP connection <0.10155.0> (IP1:48928 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:15 ===
accepting AMQP connection <0.10162.0> (IP1:48932 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:15 ===
connection <0.10155.0> (IP1:48928 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:15 ===
connection <0.10162.0> (IP1:48932 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:17 ===
accepting AMQP connection <0.10419.0> (IP1:48954 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:17 ===
connection <0.10419.0> (IP1:48954 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:29 ===
node 'rabbit@sensu-prod-rabbit-1' up

=INFO REPORT==== 26-Apr-2017::05:47:32 ===
accepting AMQP connection <0.11303.0> (IP1:49114 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:47:32 ===
connection <0.11303.0> (IP1:49114 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:47:38 ===
rabbit on node 'rabbit@sensu-prod-rabbit-1' up

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue 'results' in vhost 'sensu': Synchronising: 76 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue 'results' in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue 'results' in vhost 'sensu': Synchronising: mirrors ['rabbit@sensu-prod-rabbit-1'] to sync

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue 'results' in vhost 'sensu': Synchronising: complete

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:47:40 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:47:41 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:47:41 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:47:41 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: all slaves already synced

=ERROR REPORT==== 26-Apr-2017::05:49:07 ===
Channel error on connection <0.8488.0> (IP1:48668 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'keepalives' in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:07 ===
closing AMQP connection <0.8488.0> (IP1:48668 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:09 ===
Channel error on connection <0.8544.0> (IP1:48670 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:09 ===
closing AMQP connection <0.8544.0> (IP1:48670 -> IP2:5672):
client unexpectedly closed TCP connection

=INFO REPORT==== 26-Apr-2017::05:49:09 ===
accepting AMQP connection <0.11450.0> (IP1:50064 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:09 ===
connection <0.11450.0> (IP1:50064 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9111.0> (IP1:48764 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9111.0> (IP1:48764 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9156.0> (IP1:48792 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9156.0> (IP1:48792 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9490.0> (IP1:48820 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9135.0> (IP1:48766 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9237.0> (IP1:48818 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9135.0> (IP1:48766 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9490.0> (IP1:48820 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9237.0> (IP1:48818 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9196.0> (IP1:48810 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9196.0> (IP1:48810 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9120.0> (IP1:48756 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9085.0> (IP1:48738 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9085.0> (IP1:48738 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9120.0> (IP1:48756 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9435.0> (IP1:48824 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9435.0> (IP1:48824 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9129.0> (IP1:48762 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9508.0> (IP1:48832 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9129.0> (IP1:48762 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9171.0> (IP1:48796 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9508.0> (IP1:48832 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9566.0> (IP1:48844 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9108.0> (IP1:48748 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9159.0> (IP1:48794 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9193.0> (IP1:48804 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9171.0> (IP1:48796 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9114.0> (IP1:48754 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9193.0> (IP1:48804 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9159.0> (IP1:48794 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9108.0> (IP1:48748 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9566.0> (IP1:48844 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9114.0> (IP1:48754 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9575.0> (IP1:48864 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9186.0> (IP1:48802 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9824.0> (IP1:48884 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9575.0> (IP1:48864 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9186.0> (IP1:48802 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:16 ===
closing AMQP connection <0.9824.0> (IP1:48884 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9624.0> (IP1:48870 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9893.0> (IP1:48916 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:16 ===
Channel error on connection <0.9717.0> (IP1:48876 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9717.0> (IP1:48876 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9893.0> (IP1:48916 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9147.0> (IP1:48776 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9141.0> (IP1:48784 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9141.0> (IP1:48784 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9147.0> (IP1:48776 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9090.0> (IP1:48744 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9150.0> (IP1:48780 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9512.0> (IP1:48830 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9845.0> (IP1:48886 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9605.0> (IP1:48874 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9090.0> (IP1:48744 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9150.0> (IP1:48780 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9512.0> (IP1:48830 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9605.0> (IP1:48874 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9845.0> (IP1:48886 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9168.0> (IP1:48772 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9096.0> (IP1:48742 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9569.0> (IP1:48858 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9123.0> (IP1:48752 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9581.0> (IP1:48852 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9536.0> (IP1:48840 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9624.0> (IP1:48870 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9126.0> (IP1:48774 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9842.0> (IP1:48898 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9569.0> (IP1:48858 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9138.0> (IP1:48790 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9202.0> (IP1:48812 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9123.0> (IP1:48752 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9168.0> (IP1:48772 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9536.0> (IP1:48840 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9572.0> (IP1:48850 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9096.0> (IP1:48742 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9581.0> (IP1:48852 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9138.0> (IP1:48790 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9099.0> (IP1:48750 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9572.0> (IP1:48850 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9202.0> (IP1:48812 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9126.0> (IP1:48774 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9883.0> (IP1:48908 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9099.0> (IP1:48750 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9279.0> (IP1:48822 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9132.0> (IP1:48782 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9656.0> (IP1:48878 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9505.0> (IP1:48828 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9851.0> (IP1:48900 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9174.0> (IP1:48788 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9132.0> (IP1:48782 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9515.0> (IP1:48826 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9656.0> (IP1:48878 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9174.0> (IP1:48788 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9842.0> (IP1:48898 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9279.0> (IP1:48822 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9883.0> (IP1:48908 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9929.0> (IP1:48904 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9678.0> (IP1:48872 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9851.0> (IP1:48900 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9505.0> (IP1:48828 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9515.0> (IP1:48826 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9848.0> (IP1:48902 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9594.0> (IP1:48866 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9678.0> (IP1:48872 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9554.0> (IP1:48848 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9591.0> (IP1:48860 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9102.0> (IP1:48746 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9836.0> (IP1:48890 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9550.0> (IP1:48846 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9929.0> (IP1:48904 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9594.0> (IP1:48866 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9554.0> (IP1:48848 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9591.0> (IP1:48860 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9102.0> (IP1:48746 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9177.0> (IP1:48800 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9848.0> (IP1:48902 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9550.0> (IP1:48846 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9518.0> (IP1:48834 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9836.0> (IP1:48890 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9190.0> (IP1:48806 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9177.0> (IP1:48800 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9518.0> (IP1:48834 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9190.0> (IP1:48806 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9584.0> (IP1:48868 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9381.0> (IP1:48816 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9830.0> (IP1:48896 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9199.0> (IP1:48808 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9105.0> (IP1:48760 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9560.0> (IP1:48854 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9381.0> (IP1:48816 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9584.0> (IP1:48868 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9105.0> (IP1:48760 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9199.0> (IP1:48808 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9560.0> (IP1:48854 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9563.0> (IP1:48856 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9830.0> (IP1:48896 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9563.0> (IP1:48856 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9906.0> (IP1:48918 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9117.0> (IP1:48758 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9906.0> (IP1:48918 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9117.0> (IP1:48758 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9180.0> (IP1:48798 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9180.0> (IP1:48798 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9833.0> (IP1:48892 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9162.0> (IP1:48770 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9557.0> (IP1:48838 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9165.0> (IP1:48778 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9557.0> (IP1:48838 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9833.0> (IP1:48892 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9162.0> (IP1:48770 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9165.0> (IP1:48778 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9544.0> (IP1:48836 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9827.0> (IP1:48894 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9544.0> (IP1:48836 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9578.0> (IP1:48862 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9578.0> (IP1:48862 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9880.0> (IP1:48906 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9827.0> (IP1:48894 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9880.0> (IP1:48906 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9541.0> (IP1:48842 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9839.0> (IP1:48888 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9541.0> (IP1:48842 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9839.0> (IP1:48888 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9818.0> (IP1:48880 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9093.0> (IP1:48740 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9205.0> (IP1:48814 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9886.0> (IP1:48910 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9818.0> (IP1:48880 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9153.0> (IP1:48768 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9205.0> (IP1:48814 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9886.0> (IP1:48910 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9153.0> (IP1:48768 -> IP2:5672):
client unexpectedly closed TCP connection

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9093.0> (IP1:48740 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9821.0> (IP1:48882 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9821.0> (IP1:48882 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9903.0> (IP1:48914 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9903.0> (IP1:48914 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:17 ===
Channel error on connection <0.9889.0> (IP1:48912 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:17 ===
closing AMQP connection <0.9889.0> (IP1:48912 -> IP2:5672):
client unexpectedly closed TCP connection

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Channel error on connection <0.10155.0> (IP1:48928 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME due to timeout

=ERROR REPORT==== 26-Apr-2017::05:49:18 ===
Channel error on connection <0.10162.0> (IP1:48932 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.11647.0> (IP1:50172 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.11647.0> (IP1:50172 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.11658.0> (IP1:50180 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.11661.0> (IP1:50184 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.11658.0> (IP1:50180 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.11661.0> (IP1:50184 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.11680.0> (IP1:50188 -> IP2:5672)

=WARNING REPORT==== 26-Apr-2017::05:49:18 ===
closing AMQP connection <0.10155.0> (IP1:48928 -> IP2:5672):
client unexpectedly closed TCP connection

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.11680.0> (IP1:50188 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=WARNING REPORT==== 26-Apr-2017::05:49:18 ===
closing AMQP connection <0.10162.0> (IP1:48932 -> IP2:5672):
client unexpectedly closed TCP connection

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.11691.0> (IP1:50194 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.11691.0> (IP1:50194 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.11698.0> (IP1:50198 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.11701.0> (IP1:50202 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.11708.0> (IP1:50206 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.11698.0> (IP1:50198 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.11701.0> (IP1:50202 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
connection <0.11708.0> (IP1:50206 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.11735.0> (IP1:50212 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:18 ===
accepting AMQP connection <0.11738.0> (IP1:50216 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11735.0> (IP1:50212 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11738.0> (IP1:50216 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11757.0> (IP1:50220 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11760.0> (IP1:50224 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11757.0> (IP1:50220 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11760.0> (IP1:50224 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11775.0> (IP1:50228 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11782.0> (IP1:50232 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11775.0> (IP1:50228 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11789.0> (IP1:50236 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11792.0> (IP1:50240 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11796.0> (IP1:50248 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11801.0> (IP1:50244 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11806.0> (IP1:50252 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11782.0> (IP1:50232 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11792.0> (IP1:50240 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11789.0> (IP1:50236 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11824.0> (IP1:50256 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11796.0> (IP1:50248 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11801.0> (IP1:50244 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11806.0> (IP1:50252 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11847.0> (IP1:50260 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11858.0> (IP1:50264 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11824.0> (IP1:50256 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11869.0> (IP1:50268 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11872.0> (IP1:50272 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11847.0> (IP1:50260 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11883.0> (IP1:50276 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11858.0> (IP1:50264 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11894.0> (IP1:50280 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11901.0> (IP1:50284 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11904.0> (IP1:50288 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11907.0> (IP1:50292 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11869.0> (IP1:50268 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11914.0> (IP1:50296 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11883.0> (IP1:50276 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11894.0> (IP1:50280 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11872.0> (IP1:50272 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11929.0> (IP1:50300 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11901.0> (IP1:50284 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11904.0> (IP1:50288 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11966.0> (IP1:50308 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11914.0> (IP1:50296 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11907.0> (IP1:50292 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11976.0> (IP1:50312 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.11959.0> (IP1:50304 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11929.0> (IP1:50300 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11966.0> (IP1:50308 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.12004.0> (IP1:50316 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11959.0> (IP1:50304 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.11976.0> (IP1:50312 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.12020.0> (IP1:50320 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.12004.0> (IP1:50316 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.12020.0> (IP1:50320 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.12043.0> (IP1:50324 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.12046.0> (IP1:50328 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.12046.0> (IP1:50328 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.12053.0> (IP1:50332 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.12043.0> (IP1:50324 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.12068.0> (IP1:50336 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.12053.0> (IP1:50332 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.12079.0> (IP1:50340 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.12068.0> (IP1:50336 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.12079.0> (IP1:50340 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.12098.0> (IP1:50344 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.12101.0> (IP1:50348 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
accepting AMQP connection <0.12104.0> (IP1:50352 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.12098.0> (IP1:50344 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.12101.0> (IP1:50348 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:19 ===
connection <0.12104.0> (IP1:50352 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:20 ===
accepting AMQP connection <0.12131.0> (IP1:50356 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:20 ===
connection <0.12131.0> (IP1:50356 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=INFO REPORT==== 26-Apr-2017::05:49:21 ===
accepting AMQP connection <0.12142.0> (IP1:50370 -> IP2:5672)

=INFO REPORT==== 26-Apr-2017::05:49:22 ===
connection <0.12142.0> (IP1:50370 -> IP2:5672): user 'sensu' authenticated and granted access to vhost 'sensu'

=ERROR REPORT==== 26-Apr-2017::05:49:26 ===
Channel error on connection <0.8485.0> (IP1:48664 -> IP2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'keepalives' in vhost 'sensu' due to timeout

=WARNING REPORT==== 26-Apr-2017::05:49:26 ===
closing AMQP connection <0.8485.0> (IP1:48664 -> IP2:5672):
client unexpectedly closed TCP connection

=INFO REPORT==== 26-Apr-2017::05:49:35 ===
accepting AMQP connection <0.12156.0> (IP1:50432 -> IP2:5672)

=WARNING REPORT==== 26-Apr-2017::05:49:35 ===
closing AMQP connection <0.12156.0> (IP1:50432 -> IP2:5672):
client unexpectedly closed TCP connection

=INFO REPORT==== 26-Apr-2017::05:49:43 ===
accepting AMQP connection <0.12174.0> (IP1:50508 -> IP2:5672)

=WARNING REPORT==== 26-Apr-2017::05:49:43 ===
closing AMQP connection <0.12174.0> (IP1:50508 -> IP2:5672):
client unexpectedly closed TCP connection

=INFO REPORT==== 26-Apr-2017::05:50:24 ===
accepting AMQP connection <0.12201.0> (IP1:51050 -> IP2:5672)
{code}

Regards,
Adrian.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Karl Nilsson

Pivotal/RabbitMQ

Karl Nilsson

unread,
Apr 27, 2017, 11:55:08 AM4/27/17
to rabbitm...@googlegroups.com
Could you also try to run this rabbitmqctl command against each node:

rabbitmqctl eval "rabbit_diagnostics:maybe_stuck()."

Mirrored queue 'aliveness-test' in vhost 'sensu': Slave <rabbit@sensu-prod-rabbit-2.2.403.0> saw deaths of mirrors <rabbit@sensu-prod-rabbit-1.1.411.0>

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Promoting slave <rabbit@sensu-prod-rabbit-2.2.403.0> to master

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Slave <rabbit@sensu-prod-rabbit-2.2.603.0> saw deaths of mirrors <rabbit@sensu-prod-rabbit-1.1.615.0>

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Promoting slave <rabbit@sensu-prod-rabbit-2.2.603.0> to master

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'aliveness-test' in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'results' in vhost 'sensu': Slave <rabbit@sensu-prod-rabbit-2.2.363.0> saw deaths of mirrors <rabbit@sensu-prod-rabbit-1.1.375.0>

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'results' in vhost 'sensu': Promoting slave <rabbit@sensu-prod-rabbit-2.2.363.0> to master

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'results' in vhost 'sensu': Synchronising: 0 messages to synchronise

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'results' in vhost 'sensu': Synchronising: batch size: 4096

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue 'results' in vhost 'sensu': Synchronising: all slaves already synced

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Slave <rabbit@sensu-prod-rabbit-2.2.698.0> saw deaths of mirrors <rabbit@sensu-prod-rabbit-1.1.711.0>

=INFO REPORT==== 26-Apr-2017::05:45:24 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Promoting slave <rabbit@sensu-prod-rabbit-2.2.698.0> to master
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Karl Nilsson

Pivotal/RabbitMQ

Michael Klishin

unread,
Apr 27, 2017, 1:04:52 PM4/27/17
to rabbitm...@googlegroups.com
Your node had a message store termination. It needs restarting. The store is for transient messages,
so all of its contents would have been discarded on restart anyway.

We've only seen this once or twice before but 3.7.0 will use two message stores per vhost
instead of per node, so if this happens for any reason, only one vhost will be affected.


--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Aneci Adrian

unread,
Apr 28, 2017, 3:27:33 AM4/28/17
to rabbitm...@googlegroups.com
I've fixed this issue by resetting both nodes(rabbitmqctl reset). It is not the best solution but so far was the only one that worked. The problem is that even after I've reset the master node and excluded it from the cluster the queues still appeared on the slave node and they were still assigned to the master node (even if it wasn't anymore present in the cluster, very strange).
Queues being stuck prevented clients to put messages on these queues. Before writing a message on the queue the client check if the queue exists and create a new one if not. But in this case the queue was present but unavailable.
If it will happen again I will try to diagnostic the cluster using rabbitmqctl eval "rabbit_diagnostics:maybe_stuck()." as Karl suggested.
Can be the case that the master stopped very fast and the slave hadn't time to take over the master role?

To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

--
You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/dgjikJDu_ZM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rabbitmq-users+unsubscribe@googlegroups.com.

Michael Klishin

unread,
Apr 28, 2017, 4:35:40 AM4/28/17
to rabbitm...@googlegroups.com, Aneci Adrian
There are no master or slave nodes. Queues have a master and 0 or more mirrors, nodes are all identical.

I explained how to interpret what stands out in the logs: one of the nodes had an unrecoverable exception in
the message store. Resetting both nodes was not necessary but it's too late to debate that.

I don't remember if we tried reproducing the case where queue master isn't migrated when a node
is removed from the cluster but it is a known issue for non-mirrored nodes:
https://github.com/rabbitmq/rabbitmq-server/issues/1049

On 28 April 2017 at 09:27:33, Aneci Adrian (aneci....@gmail.com) wrote:
> I've fixed this issue by resetting both nodes(rabbitmqctl reset). It is not
> the best solution but so far was the only one that worked. The problem is
> that even after I've reset the master node and excluded it from the cluster
> the queues still appeared on the slave node and they were still assigned to
> the master node (even if it wasn't anymore present in the cluster, very
> strange).
> Queues being stuck prevented clients to put messages on these queues.
> Before writing a message on the queue the client check if the queue exists
> and create a new one if not. But in this case the queue was present but
> unavailable.
> If it will happen again I will try to diagnostic the cluster using rabbitmqctl
> eval "rabbit_diagnostics:maybe_stuck()." as Karl suggested.
> Can be the case that the master stopped very fast and the slave hadn't time
> to take over the master role?
>
> 2017-04-27 20:04 GMT+03:00 Michael Klishin :
>
> > Your node had a message store termination. It needs restarting. The store
> > is for transient messages,
> > so all of its contents would have been discarded on restart anyway.
> >
> > We've only seen this once or twice before but 3.7.0 will use two message
> > stores per vhost
> > instead of per node, so if this happens for any reason, only one vhost
> > will be affected.
> >
> >
> > On Thu, Apr 27, 2017 at 11:28 AM, Aneci Adrian
> >> <0.919.0>,undefined,#Fun> >> t_variable_queue.20.118228399>},
> >> infinity]}}
> >>
> >>
> >> =ERROR REPORT==== 19-Apr-2017::09:43:04 ===
> >> Discarding message {'$gen_call',{<0.16596.1>,#Ref<0.0.2.48068>},stat}
> >> from <0.16596.1> to <0.6006.0> in an old incarnation (1) of this node (3)
> >>
> >> =ERROR REPORT==== 26-Apr-2017::05:47:38 ===
> >> Discarding message {'$gen_call',{<0.11897.0>,#Ref<0.0.2.3095>},stat}
> >> from <0.11897.0> to <0.499.0> in an old incarnation (1) of this node (3)
> >>
> >> =WARNING REPORT==== 26-Apr-2017::05:47:38 ===
> >> msg_store_persistent: rebuilding indices from scratch
> >>
> >> =ERROR REPORT==== 26-Apr-2017::05:50:22 ===
> >> Channel error on connection <0.2687.5> (10.104.100.242:51852 ->
> >> 172.18.0.2:5672, vhost: 'sensu', user: 'sensu'), channel 1:
> >> operation queue.declare caused a channel exception not_found: failed to
> >> perform operation on queue 'QUEUE_NAME' in vhost 'sensu' due to timeout
> >>
> >> Can you please give us a hist what can be the problem? Can be a bug?
> >> Thank you!
> >>
> >> Regards,
> >> Adrian.
> >>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "rabbitmq-users" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an
> >> email to rabbitmq-user...@googlegroups.com.
> >> To post to this group, send email to rabbitm...@googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >>
> >
> >
> >
> > --
> > MK
> >
> > Staff Software Engineer, Pivotal/RabbitMQ
> >
> > --
> > You received this message because you are subscribed to a topic in the
> > Google Groups "rabbitmq-users" group.
> > To unsubscribe from this topic, visit https://groups.google.com/d/
> > topic/rabbitmq-users/dgjikJDu_ZM/unsubscribe.
> > To unsubscribe from this group and all its topics, send an email to
> > rabbitmq-user...@googlegroups.com.
> > To post to this group, send email to rabbitm...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
> --
> You received this message because you are subscribed to the Google Groups "rabbitmq-users"
> group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
> To post to this group, send an email to rabbitm...@googlegroups.com.

V Z

unread,
May 1, 2017, 1:44:39 PM5/1/17
to rabbitmq-users, aneci....@gmail.com
Michael, would you please summarize the recommended recovery procedure? 

Several times we've run into the issue of a queue appearing in the management UI with question marks and no HA policy (even though one should have applied). I am not sure if that was this same issue or just symptomatically similar. We could only recover the queue (so that it appears with numbers and policy and consumers can connect to it) by deleting and recreating the queue and restarting the cluster after several haphazard attempts.

Aneci Adrian

unread,
Jun 6, 2017, 7:09:54 AM6/6/17
to rabbitmq-users, aneci....@gmail.com
All queues are mirrored based on a HA-policy (ha-mode:all, ha-sync-mode:automatic) and have auto-delete option set to true.
I've tried to avoid resetting both nodes but after resetting the queues master, the queues from the mirrored node entered in a fail state and couldn't be even manually deleted so I had to reset also this node. Also, the server on which the queues master rely had a normal reboot and not a forced one. 
In my opinion the issue from https://github.com/rabbitmq/rabbitmq-server/issues/1049 is not applicable in this case.

Aneci Adrian

unread,
Jun 6, 2017, 7:10:29 AM6/6/17
to rabbitmq-users, aneci....@gmail.com
I've find a queue that is in a fail state. The ha-policy is not applied anymore for some reason and it is not mirrored and also not running.
I' ve run rabbitmqctl eval "rabbit_diagnostics:maybe_stuck()." on the queues master and didn't found anything suspicious. Below is the output:

rabbitmqctl eval "rabbit_diagnostics:maybe_stuck()."
2017-04-28 12:01:36 There are 2365 processes.
2017-04-28 12:01:36 Investigated 0 processes this round, 5000ms to go.
2017-04-28 12:01:36 Investigated 0 processes this round, 4500ms to go.
2017-04-28 12:01:37 Investigated 0 processes this round, 4000ms to go.
2017-04-28 12:01:37 Investigated 0 processes this round, 3500ms to go.
2017-04-28 12:01:38 Investigated 0 processes this round, 3000ms to go.
2017-04-28 12:01:38 Investigated 0 processes this round, 2500ms to go.
2017-04-28 12:01:39 Investigated 0 processes this round, 2000ms to go.
2017-04-28 12:01:39 Investigated 0 processes this round, 1500ms to go.
2017-04-28 12:01:40 Investigated 0 processes this round, 1000ms to go.
2017-04-28 12:01:40 Investigated 0 processes this round, 500ms to go.
2017-04-28 12:01:41 Found 0 suspicious processes.
ok

A grep based on the queue name in the rabbitmq log showed that the queue was synchronized at 11:26 and half an hour later an operation failure error was raised for the same queue:

=INFO REPORT==== 28-Apr-2017::11:26:57 ===
Mirrored queue QUEUE_NAME in vhost 'sensu': Synchronising: all slaves already synced
--
=ERROR REPORT==== 28-Apr-2017::11:59:23 ===
Channel error on connection <0.27128.4> (<rabbit@sensu-int-rabbit-1.1.27128.4>, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.delete caused a channel exception not_found: failed to perform operation on queue QUEUE_NAME in vhost 'sensu' due to timeout

Michael Klishin

unread,
Jun 6, 2017, 7:36:29 AM6/6/17
to rabbitm...@googlegroups.com, Aneci Adrian
You can forcefully delete a queue so that your apps can then re-declare it:

rabbitmqctl eval '{ok, Q} = rabbit_amqqueue:lookup(rabbit_misc:r(<<"VHOST_NAME">>, queue, <<"QUEUE_NAME">>)), Pid = rabbit_amqqueue:pid_of(Q), rabbit_amqqueue:delete_immediately([Pid]).'

in some cases (when the entire node where the queue was hosted is not reachable) it has to be done differently:

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Aneci Adrian

unread,
Jun 7, 2017, 7:00:41 AM6/7/17
to rabbitmq-users, aneci....@gmail.com
The same issue reoccurred. The queue is not removed using the suggested command. It returns true but the queue is still present in rabbitmq UI.
Some relevant logs:

=ERROR REPORT==== 3-Jun-2017::19:53:33 ===
Error on AMQP connection <0.16788.0> (10.134.6.34:55870 -> 172.18.0.3:5672, vhost: 'sensu', user: 'sensu', state: running), channel 0:
operation none caused a connection exception connection_forced: "broker forced connection closure with reason 'shutdown'"

=ERROR REPORT==== 3-Jun-2017::19:53:49 ===
Discarding message {'$gen_call',{<0.3365.0>,#Ref<0.0.3.1522>},stat} from <0.3365.0> to <0.10974.0> in an old incarnation (1) of this node (3)  

=ERROR REPORT==== 3-Jun-2017::19:59:41 ===
Channel error on connection <0.4884.6> (10.134.6.34:49082 -> 172.18.0.3:5672, vhost: 'sensu', user: 'sensu'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue '<queue_name>' in vhost 'sensu' due to timeout

Also I can see for example that there are 2 queues for the same client, one that is working and one which seems to be stuck(neither running nor ha policy applied).



By running rabbitmqctl list_queues name -p sensu I've got only 46 queues while in the rabbitmq UI there are over 100 queues present.

Regards,
Adrian.

Riccardo Pittau

unread,
Jul 27, 2017, 7:31:55 PM7/27/17
to rabbitmq-users, aneci....@gmail.com
Hi all

we've also experienced this issue and we've been able to remove the queue using this command:

rabbitmqctl eval 'Q = {resource, <<"VHOST NAME">>, queue, <<"QUEUE NAME">>}, rabbit_amqqueue:internal_delete(Q).'

The queue was successfully deleted and recreated.

Anyway, hope a fix will be released soon.

Thanks

Rik

xiya...@gmail.com

unread,
Apr 18, 2019, 5:33:19 AM4/18/19
to rabbitmq-users
Today, some of my queues are also in the NaN state. The queue has no HA policy and cannot be deleted. In addition, rabbitmq reports "operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'QUEUE_NAME' in vhost '/' Due to timeout". Later I restarted rabbitmq and everything is back to normal. My version is rabbitmq 3.7.5, Erlang 20.1.7. Is this a bug for rabbitmq or erlang? I hope you can give me some suggestions? Thank you very much!

在 2017年4月27日星期四 UTC+8下午5:28:05,Aneci Adrian写道:

Michael Klishin

unread,
Apr 18, 2019, 10:23:00 AM4/18/19
to rabbitmq-users
We don't have enough information to suggest anything. It is very unlikely something Erlang-specific.
Please start a new thread (and upgrade to RabbitMQ 3.7.14, Erlang 20.3+). 3.7.5 is close to 1 year old.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

xiya...@gmail.com

unread,
Apr 22, 2019, 3:24:22 AM4/22/19
to rabbitmq-users
Hello! Recently, our team is testing the problems related to network failure recovery. I found that after the network partition is over, the individual queues of rabbitmq will have NaN status. I think this is a reliable means of recurrence. Here are some logs!
[root@position-node1 privatecloud]# kubectl logs -f rabbitmq-c0a8669a-0 | grep ERROR
2019-04-22 12:43:32.973 [error] <0.159.0> Mnesia('rab...@192.168.102.154'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, 'rab...@192.168.102.237'}
2019-04-22 12:51:11.347 [error] <0.159.0> Mnesia('rab...@192.168.102.154'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, 'rab...@192.168.102.44'}
2019-04-22 13:40:40.505 [error] <0.159.0> Mnesia('rab...@192.168.102.154'): ** ERROR ** mnesia_event got {inconsistent_database, running_partitioned_network, 'rab...@192.168.102.237'}
^C
您在 /var/spool/mail/root 中有邮件
[root@position-node1 privatecloud]# kubectl logs -f rabbitmq-c0a8662c-0 | grep ERROR
2019-04-22 12:51:19.235 [error] <0.180.0> Mnesia('rab...@192.168.102.44'): ** ERROR ** mnesia_event got {inconsistent_database, running_partitioned_network, 'rab...@192.168.102.237'}
2019-04-22 12:51:19.920 [error] <0.180.0> Mnesia('rab...@192.168.102.44'): ** ERROR ** mnesia_event got {inconsistent_database, running_partitioned_network, 'rab...@192.168.102.154'}
2019-04-22 12:51:19.923 [error] <0.180.0> Mnesia('rab...@192.168.102.44'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, 'rab...@192.168.102.154'}
2019-04-22 13:40:39.627 [error] <0.11154.0> Mnesia('rab...@192.168.102.44'): ** ERROR ** mnesia_event got {inconsistent_database, running_partitioned_network, 'rab...@192.168.102.237'}
^C
[root@position-node1 privatecloud]# kubectl logs -f rabbitmq-c0a866ed-0 | grep ERROR
2019-04-22 12:41:34.626 [error] <0.159.0> Mnesia('rab...@192.168.102.237'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, 'rab...@192.168.102.154'}
2019-04-22 12:43:26.264 [error] <0.159.0> Mnesia('rab...@192.168.102.237'): ** ERROR ** mnesia_event got {inconsistent_database, running_partitioned_network, 'rab...@192.168.102.154'}
2019-04-22 12:43:33.799 [error] <0.159.0> Mnesia('rab...@192.168.102.237'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, 'rab...@192.168.102.154'}
2019-04-22 12:50:13.211 [error] <0.4421.0> Mnesia('rab...@192.168.102.237'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, 'rab...@192.168.102.154'}
2019-04-22 12:51:19.013 [error] <0.4421.0> Mnesia('rab...@192.168.102.237'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, 'rab...@192.168.102.44'}
2019-04-22 14:07:30.895 [error] <0.4421.0> Mnesia('rab...@192.168.102.237'): ** ERROR ** mnesia_event got {inconsistent_database, running_partitioned_network, 'rab...@192.168.102.154'}
2019-04-22 14:07:38.116 [error] <0.4421.0> Mnesia('rab...@192.168.102.237'): ** ERROR ** mnesia_event got {inconsistent_database, running_partitioned_network, 'rab...@192.168.102.44'}
2019-04-22 14:08:46.503 [error] <0.19200.1> Mnesia('rab...@192.168.102.237'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, 'rab...@192.168.102.154'}
2019-04-22 14:08:46.503 [error] <0.19200.1> Mnesia('rab...@192.168.102.237'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, 'rab...@192.168.102.44'}


There are some key configurations:cluster_partition_handling = pause_minority; three MQ nodes
ha-mode:exactly
ha-params:2
ha-promote-on-failure:always
ha-promote-on-shutdown:always
ha-sync-mode:automatic
max-length:100000

If you still need more information, please reply me, thank you



在 2019年4月18日星期四 UTC+8下午10:23:00,Michael Klishin写道:
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitm...@googlegroups.com.

To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Michael Klishin

unread,
Apr 22, 2019, 7:13:55 AM4/22/19
to rabbitmq-users
Please start a new thread after upgrading to 3.7.14.

All these grepped entries tell us is that all 3 nodes have experienced partitions
(in case of 2019-04-22 12:51:11 and 2019-04-22 12:51:19, possibly even at the same time).

We cannot see any other events due to grep. RabbitMQ 3.6.x has been EOL'ed in May 2018.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.

To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

xiya...@gmail.com

unread,
Apr 23, 2019, 5:50:10 AM4/23/19
to rabbitmq-users
Today, this problem has arisen again. I intercepted some errors. Please see if there is any problem. Recently, I have been depressed by this problem.

My cluster version and configuration information, you can view the information I replied before.

Thank you very much.

在 2019年4月22日星期一 UTC+8下午7:13:55,Michael Klishin写道:
rabbitmq.txt

Michael Klishin

unread,
Apr 23, 2019, 8:40:54 AM4/23/19
to rabbitmq-users
We have asked for a new thread to be started two times. Hijacking existing discussions is confusing to everyone and strongly discouraged on this list.
If you are looking for help, please cooperate with list moderators (I am one of them). I am locking this thread.

According to the log entries a mirror promotion failed because of an exception in the broadcast module. I don't recall seeing this
on this list or in known issues.  Please upgrade to 3.7.14  regardless and consider running 3 nodes instead of 2.
It is not generally possible for 2 nodes to reach consensus.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.

To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages