[rabbitmq-discuss] Removing "INFO REPORT" from logs (due to 30gb log file in 1 day)

Thu Jun 23 16:49:38 BST 2011

Hi Alvaro,

I had seen a similar post on the list (I think from Matthias) which explains
how to fix using this approach, but thank you for taking the time to explain
this anyway!

Cal

On Thu, Jun 23, 2011 at 4:48 PM, Alvaro Videla <videlalvaro at gmail.com>wrote:

> Hi,
>
> According to the Erlang docs you can disable both SASL and rabbit logs by
> passing the following parameters to the rabbitmq-server init script:
>
> sbin/rabbitmq-server -kernel error_logger silent -sasl sasl_error_logger
> false
>
> More docs on the topic here:
>
> SASL Logs: http://www.erlang.org/doc/man/sasl_app.html
> Erlang Kernel Docs: http://www.erlang.org/doc/man/kernel_app.html
>
> Regarding specifying those parameters in a config file, that's possible
> too.
>
> You can add them to this file for example:
> http://www.rabbitmq.com/configure.html#config-file
>
> So there you could add an entry like this:
>
> {sasl, [
> {sasl_error_logger, false}
> ]}
>
> For the SASL logs
>
> And another one like:
>
> {kernel [
> {error_logger, silent}
> ]}
>
> The problem with this approach is that the command line arguments passed
> inside the rabbitmq-server script will override what you put on those
> .config files, as explained here:
> http://www.erlang.org/doc/man/config.html
>
> "Configuration parameter values in the configuration file will override
> the values in the application resource files (see app(4)). The values in
> the configuration file can be overridden by command line flags (see erl(1)
> )."
>
>  I think some tweaking of the rabbitmq-server script will do to solve this
> problem, specifically this lines:
>
>     -sasl errlog_type error \
>     -kernel error_logger '{file,"'${RABBITMQ_LOGS}'"}' \
>     -sasl sasl_error_logger '{file,"'${RABBITMQ_SASL_LOGS}'"}' \
>
> Hope this helps,
>
> Alvaro
>
> On Jun 23, 2011, at 4:47 PM, Cal Leeming [Simplicity Media Ltd] wrote:
>
> Alright great :) Thanks for the advice on how to resolve the problem in the
> mean time.
>
> Ironically, it's actually a good thing that this happened, because it's
> notified me of a 'looping' bug in my code (in a round abouts way), which
> caused a DoS :)
>
> Cal
>
> On Thu, Jun 23, 2011 at 3:43 PM, Matthew Sackman <matthew at rabbitmq.com>wrote:
>
>> On Thu, Jun 23, 2011 at 03:40:59PM +0100, Cal Leeming [Simplicity Media
>> Ltd] wrote:
>> > Hmm, are there any plans to make this easier for a user to change via
>> the
>> > config?? Almost every other daemon I know has support for this, so it
>> makes
>> > RabbitMQ terribly unfriendly :(
>>
>> Yes, we have been thinking about this on and off for quite some time.
>> I'm not sure what the current plans are wrt this, but you're not the
>> first person to point out this problem, and we do have a bug open to
>> look at sorting this out.
>>
>> Matthew
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
> Sent form my Nokia 1100
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110623/c9a8d0f4/attachment.htm>