Log Queue Threshold (1000) Exceeded. Discarding New Messages.

Home » Asterisk Users » Log Queue Threshold (1000) Exceeded. Discarding New Messages.
Asterisk Users 2 Comments

Hi.

I’ve just upgraded from Asterisk 13 to Asterisk 16 (as part of a Debian &
Devuan version upgrade).

Whenever Asterisk starts, I’m now getting entries such as the following in my log file:

WARNING[13905]: logger:0 in ***: Log queue threshold (1000) exceeded. Discarding new messages.

Where can I set this threshold?

I don’t want the system to discard new messages – mainly because the very last message displayed is supposed to be “Asterisk Ready”, and one of our monitoring system checks for this and complains if it’s not found (because it then looks like Asterisk didn’t start up properly).

I’m also pretty certain that the system is discarding *all* messages beyond the threshold – even if they’re errors rather than just warnings or verbose output – and obviously I want to see any errors which are detected.

I assume there’s some new setting in logger.conf which I need to adjust, but I
haven’t found it documented yet 🙁

Thanks,

Antony.


The next sentence is untrue. The previous sentence is also not true.

Please reply to the list;
please *don’t* CC me.

2 thoughts on - Log Queue Threshold (1000) Exceeded. Discarding New Messages.

  • /etc/asterisk/logger.conf

    ; All log messages go to a queue serviced by a single thread
    ; which does all the IO.  This setting controls how big that
    ; queue can get (and therefore how much memory is allocated)
    ; before new messages are discarded.
    ; The default is 1000

    Doug

  • logger_queue_limit

    Ah, thanks.

    I didn’t see that because the upgrade process kept my existing logger.conf instead of over-writing it with the new Asterisk 16 version (for which I’m grateful, since it has my own settings in it).

    https://github.com/asterisk/asterisk/blob/master/configs/samples/logger.conf.sample gave me the information I needed though – just a pity I didn’t find that when looking up the error message 🙁

    Regards,

    Antony.


    A user interface is like a joke. If you have to explain it, it means it doesn’t work.

    Please reply to the list;
    please *don’t* CC me.