RabbitMQ lager_error_logger_h dropped 6 messages

[Michael G]

Hi,

I use the RabbitMQ Version: 3.7.11 and Erlang Version: 21.2. I have seen  the error 

2019-04-04 09:30:54.016 [warning] <0.114.0> lager_error_logger_h dropped 1 messages in the last second that exceeded the limit of 1000 messages/sec

appears from time to time in the rabbitmq logs (C:\Users\MyUser\AppData\Roaming\RabbitMQ\log\rabbit@MyMachineRabbitMQ). Now I change the rabbitmq.config

[

{rabbit,

[

{tcp_listeners, [5672]},

{loopback_users, []}

]

},

{lager,

[

{error_logger_hwm, 1800}

]}

].

and icreased the error_logger_hwm to 1800. Now, the error appears less, but still:

2019-04-04 09:47:54.016 [warning] <0.114.0> lager_error_logger_h dropped 6 messages in the last second that exceeded the limit of 1800 messages/sec. 

Now, I inreased the level again to 4000 and I have recognized no new errors. Despite increasing the level I recognized no new error logs. So, I'm confused because after increasing the value I thought a lot of errors will appear in the log file. Since this is not the case, is the error related to RabbitMQ or a different problem with erlang? How, can I locate the reason for this error?

[po...@platform9.com]

I assume these are just log messages getting dropped, and not the actual RPC message itself?

[Kevin Freeman]

My understanding after being frustrated by this message myself is that the logger is calculating the message rate based _all_ incoming messages, not just those messages that meet the configured log level.  i.e. there could be a flood of INFO messages while consumers are spinning up.  There is no way of knowing if the dropped messages are above or below the configured log level (DEBUG, INFO, WARN, ERROR, etc).

Kevin

[Grigory Starinkin]

Hi,

This fix, I think, should be able to help with the incorrect counting: 

https://github.com/erlang-lager/lager/issues/496

Grigory Starinkin 

On 17 Apr 2019, at 19:43, Kevin Freeman <kfre...@gmail.com> wrote:

My understanding after being frustrated by this message myself is that the logger is calculating the message rate based _all_ incoming messages, not just those messages that meet the configured log level.  i.e. there could be a flood of INFO messages while consumers are spinning up.  There is no way of knowing if the dropped messages are above or below the configured log level (DEBUG, INFO, WARN, ERROR, etc).

Kevin

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

[Luke Bakken]

Hello,

The following fix has been merged: https://github.com/erlang-lager/lager/pull/499

Expect to see this ship with RabbitMQ 3.7.15

Thanks,
Luke

On Wednesday, April 17, 2019 at 12:43:17 PM UTC-7, Grigory Starinkin wrote:

Hi,

This fix, I think, should be able to help with the incorrect counting: 

https://github.com/erlang-lager/lager/issues/496

Grigory Starinkin 

On 17 Apr 2019, at 19:43, Kevin Freeman <kfre...@gmail.com> wrote:

My understanding after being frustrated by this message myself is that the logger is calculating the message rate based _all_ incoming messages, not just those messages that meet the configured log level.  i.e. there could be a flood of INFO messages while consumers are spinning up.  There is no way of knowing if the dropped messages are above or below the configured log level (DEBUG, INFO, WARN, ERROR, etc).

Kevin

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

[Ernani Rodrigues de São Thiago]

RabbitMQ 3.7.15-beta.1 is out, does it contains this fix? How long do you think till 3.7.15 stable release?

Best Regards, Ernani

Em terça-feira, 30 de abril de 2019 21:51:24 UTC-3, Luke Bakken escreveu:

Hello,

The following fix has been merged: https://github.com/erlang-lager/lager/pull/499

Expect to see this ship with RabbitMQ 3.7.15

Thanks,
Luke

On Wednesday, April 17, 2019 at 12:43:17 PM UTC-7, Grigory Starinkin wrote:

Hi,

This fix, I think, should be able to help with the incorrect counting: 

https://github.com/erlang-lager/lager/issues/496

Grigory Starinkin 

On 17 Apr 2019, at 19:43, Kevin Freeman <kfre...@gmail.com> wrote:

My understanding after being frustrated by this message myself is that the logger is calculating the message rate based _all_ incoming messages, not just those messages that meet the configured log level.  i.e. there could be a flood of INFO messages while consumers are spinning up.  There is no way of knowing if the dropped messages are above or below the configured log level (DEBUG, INFO, WARN, ERROR, etc).

Kevin

--
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 rabbitm...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

[Michael Klishin]

It does contain a patched version of Lager. There is a rough timeline mentioned in the 3.7.15-beta.1 announcement

on this list from earlier today.

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.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/58fcce81-c622-43a9-adc2-6ddfa3450cfc%40googlegroups.com.

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

--

MK

Staff Software Engineer, Pivotal/RabbitMQ