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

Matthew Sackman matthew at rabbitmq.com
Thu Jun 23 15:38:29 BST 2011

On Thu, Jun 23, 2011 at 03:34:20PM +0100, Cal Leeming [Simplicity Media Ltd] wrote:
> So my server died a horrible death when all the disk space was used due to
> this:
>  root at mysql01 [/var/log/rabbitmq] > ls -lah
> total 38G
> drwxr-xr-x  2 sshd ssh  4.0K Jun 19 07:25 .
> drwxr-xr-x 10 root root 4.0K Jun 23 07:25 ..
> -rw-r--r--  1 sshd ssh   38G Jun 23 01:45 rabbit at mysql01.log
>  root at mysql01 [/var/log/rabbitmq] > head rabbit at mysql01.log -n 2
> =INFO REPORT==== 19-Jun-2011::06:25:19 ===
> So, is there any way to actually stop those "INFO REPORT" messages from
> being logged, but keep the error logs? I saw the thing about patching the
> start up scripts (but that disables all logging, including errors, and seems
> terribly hacky :S)

I'm afraid there's no solution to this atm merely by configuration. If
you're happy compiling from source then in rabbit_log.erl, you should
find some lines:

handle_cast({info, Fmt}, State) ->
    {noreply, State};
handle_cast({info, Fmt, Args}, State) ->
    error_logger:info_msg(Fmt, Args),
    {noreply, State};

If you just entirely remove the error_logger:info_msg lines and
recompile then you'll lose info messages (you'll get warnings when
compiling about unused vars, but don't worry about that).


More information about the rabbitmq-discuss mailing list