debug log_level in rabbitMQ configuration

[Nilesh Vijaywargiay]

Which version did rabbitMQ introduced debug as one of the option for log_levels ? 

We are experiencing a possible slowness for 15 seconds from rabbitMQ now and then and want to investigate further by enabling debug level logging. We are on 3.3.5 version

Nick.

[Michael Klishin]

On 10 December 2015 at 08:13:14, Nilesh Vijaywargiay (nilesh...@gmail.com) wrote:
> Which version did rabbitMQ introduced debug as one of the option
> for log_levels ?

None. We are replacing logging with something Lager-based after 3.6.0 ships, this would
introduce a debug severity. 

> We are experiencing a possible slowness for 15 seconds from rabbitMQ
> now and then and want to investigate further by enabling debug
> level logging.

There is no debug logging that would help you with that, although Erlang has plenty
of tooling for monitoring of running systems.

Upgrade to 3.5.6, good chances are, this is https://github.com/rabbitmq/rabbitmq-server/issues/227.
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Nilesh Vijaywargiay]

Thanks for the response Michael.

I tried adding debug option for 3.5.3 version and it seem to have started the rabbitMQ server. 

[

 {rabbit, [{log_levels, [{connection, debug}, {channel, info}]}]}

].

Earlier when I tried this operation with 3.3.5, rabbitMQ server wouldn't even start. Since 3.5.3 did start with debug option, it made me think that debug level logging is available in 3.5.3. 

Also - https://github.com/rabbitmq/rabbitmq-server/issues/227 was raised in July 2015 where as 3.5.3 was released August 2014. Makes me doubt if it could be because of that issue hence need to confirm. 

[Michael Klishin]

On 10 December 2015 at 12:05:05, Nilesh Vijaywargiay (nilesh...@gmail.com) wrote:
> Also - https://github.com/rabbitmq/rabbitmq-server/issues/227 
> was raised in July 2015 where as 3.5.3 was released August 2014.
> Makes me doubt if it could be because of that issue hence need to
> confirm.

3.5.3 was released in May 2015:
http://www.rabbitmq.com/changelog.html

and obviously does not include server#227. 3.5.6 does. 

[Nilesh Vijaywargiay]

sorry I meant 3.3.5 since that's what we are on. 

Could you also comment on why would rabbitmq 3.3.5 not start with debug option in log_levels where as 3.5.3 rabbitmq starts just fine. I have this question since you mentioned there is no debug level logging yet. 

[Michael Klishin]

On 10 December 2015 at 12:12:27, Nilesh Vijaywargiay (nilesh...@gmail.com) wrote:
> Could you also comment on why would rabbitmq 3.3.5 not start
> with debug option in log_levels where as 3.5.3 rabbitmq starts
> just fine. I have this question since you mentioned there is no
> debug level logging yet.

When I mean "there is no debug logging" I mean that there is very little operational
information that's logged at debug or any other level that's not supposed to be enabled most of the time. Whether "debug" is treated as a valid log level or not, it does not even matter.

There are plugins such as event exchange and tracing that provide more info. However,
they wouldn't help much for your case, while profiling and live introspection tools can.

Again, perhaps  the easiest course of action is to upgrade to 3.5.6.

[ediga venki]

Hi,

I am also using same version and enabled debug log level option { log_levels, [{connection, debug} , {channel ,debug}]}.

So, rabbitmq server has running on VMware.

Step 1:

I tested on ubuntu(client has running on VMware ubuntu ),it's working and able to see the MQTT accepting TCP connection messages.

Step 2:

I tested with LPC Board(client), So I observed client log and getting 104 error during handshake time.

But i can't see any information on server side.

Note :

This version supports ECC certificates and ciphers.

[Michael Klishin]

Please start new threads for new questions (which you already have and we asked for details). 

> --
> 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.