rabbitmq 3.6.5 debug log level not working

2,721 views
Skip to first unread message

rakar...@gmail.com

unread,
Mar 15, 2017, 10:40:19 AM3/15/17
to rabbitmq-users
Hi,

Am using rabbitmq  3.6.5 where I enabled debug, but not seeing any debug information on rabbitmq log file.

Here is my rabbitmq.config file,

=====================
[
 {rabbitmq_stomp, [{tcp_listeners, [{"xxx.xxx.xxx.xxx", 61614}]}]},
 {rabbit, [{reverse_dns_lookups, true},{cluster_partition_handling, ignore},{log_levels, [{connection, debug}, {channel, debug}, {federation, debug}]}]},
 {rabbitmq_management, [{rates_mode, basic}]}
].
=====================

after this I restarted rabbitmq services and still seeing below logs only and not seeing debug logs,

=====================
=INFO REPORT==== 15-Mar-2017::09:22:27 ===
accepting STOMP connection <0.4939.0> (user-server:63294 -> central-server:61614)

=INFO REPORT==== 15-Mar-2017::09:22:28 ===
Federation queue 'stomp-subscription-xAPJTNVJxAp4ZF8D4Y7bXA' in vhost '/userdetails' connected to queue 'stomp-subscription-xAPJTNVJxAp4ZF8D4Y7bXA' in vhost '/userdetails' on amqp://site-server

=INFO REPORT==== 15-Mar-2017::09:22:28 ===
accepting AMQP connection <0.4988.0> (site-server:40869 -> central-server:5672)

=INFO REPORT==== 15-Mar-2017::09:22:33 ===
closing AMQP connection <0.4988.0> (site-server:40869 -> central-server:5672)

=INFO REPORT==== 15-Mar-2017::09:22:33 ===
Federation queue 'stomp-subscription-xAPJTNVJxAp4ZF8D4Y7bXA' in vhost '/userdetails' disconnecting from queue 'stomp-subscription-xAPJTNVJxAp4ZF8D4Y7bXA' in vhost '/userdetails' on amqp://site-server

=INFO REPORT==== 15-Mar-2017::09:22:33 ===
closing STOMP connection <0.4939.0> (user-server:63294 -> central-server:61614)
=====================

Can somebody let me know how to enable debug log on this version?


Regards
Ravi

Michael Klishin

unread,
Mar 15, 2017, 10:44:56 AM3/15/17
to rabbitm...@googlegroups.com, rakar...@gmail.com
There's very little debug logging in 3.6.x (or earlier) but there is a separate log file, rabbitmq…-sasl.log,
which logs all unhandled exceptions/process terminations.

In most cases debug logging isn't as useful as Erlang tracing capabilities or a traffic capture
(see https://www.rabbitmq.com/amqp-wireshark.html).

3.7.0 will have only one file and more debug logging.
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

--
MK

Staff Software Engineer, Pivotal/RabbitMQ


rakar...@gmail.com

unread,
Mar 15, 2017, 12:22:45 PM3/15/17
to rabbitmq-users, rakar...@gmail.com
Oh ok. So how can I do debugging the rabbitmw? Since am facing some issue bi-directional federation exchange.

I tried with wireshark and found something unknown exchange, basically when I publish the broadcast message it travel from A -> B rabbitmq cluster and consumer will consume that message and will publish back the new reply message as exchange which should be forwarded from B -> A. In this return travel the messages are getting lost which I need to troubleshoot to find it out.


Regards
Ravi

Michael Klishin

unread,
Mar 15, 2017, 12:34:36 PM3/15/17
to rabbitm...@googlegroups.com
RabbitMQ never logs messages flowing through it.


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.

rakar...@gmail.com

unread,
Mar 15, 2017, 12:43:11 PM3/15/17
to rabbitmq-users
Ok. Let me try this.

By the way when we can expect the release of 3.7.0?


Regards
Ravi
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
0 new messages