ejabberd - Comments for "Logfile Rollover"

Thanks, I'll give that a

zengargoyle — Sat, 24 Jun 2006 12:53:18 +0000

Thanks, I'll give that a try. I think I put that there when testing from the erl shell outside of ejabberd and needed that to make it work.

Simply don't start crypto

teo — Fri, 23 Jun 2006 19:39:45 +0000

Simply don't start crypto server every time. And since it is launched by ejabberd itself you don't have to start it at all.

Bummer, I'm using a custom

zengargoyle — Fri, 23 Jun 2006 15:52:19 +0000

Bummer, I'm using a custom authentication module that needs to use MD5. It seems that I get tons of crypto_server start and stop messages.

Quote:

=PROGRESS REPORT==== 23-Jun-2006::10:28:29 ===
application: crypto
started_at: 'ejabberd@chat.myserver.com'

=PROGRESS REPORT==== 23-Jun-2006::10:35:21 ===
supervisor: {local,crypto_sup}
started: [{pid,<0.29463.1>},
{name,crypto_server},
{mfa,{crypto_server,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]

=PROGRESS REPORT==== 23-Jun-2006::10:35:21 ===
application: crypto
started_at: 'ejabberd@chat.myserver.com'

I think that comes from this:

Quote:

get_query(User, Password) ->
crypto:start(),
Pass = crypto:md5(Password),
crypto:stop(),
Pas = as_hex(binary_to_list(Pass)),
L = lists:concat([User,"@",Pas]),
Q = as_hex(L),
Q.

So, am I doing anything horribly wrong here? (total Erlang newbie). Or is there anyway to stop crypto_server from logging? I'm getting about 1MB per week in sasl.log.

There's no command which

teo — Thu, 22 Jun 2006 15:04:16 +0000

There's no command which reopens sasl.log. But it shouldn't grow fast. Ideally it shouln't grow at all. And it would be a good idea to report error (crash) messages from it. Usually they indicate bugs (may be noncritical).

Logfile Rollover for sasl.log

zengargoyle — Thu, 22 Jun 2006 11:23:55 +0000

I've tried the 'ejabberdctl reopen-log' command and it works for the main ejabberd.log file. Is there another command to rotate the sasl.log file? I can't get that one to rotate correctly, ejabberd continues to log to the old file.

ejabberd has a command to

sander — Fri, 04 Nov 2005 09:33:13 +0000

ejabberd has a command to reopen the log:

ejabberdctl node reopen-log

You just need a tool like lograte that:

Checks for example from time to time the size of the logs.
When it is bigger than a configured size, it will:
archive the logs to something like ejabberd-log-20051104.tar.gz,
delete the current log file,
create a new, empty file,
run the above ejabberdctl command.

--
sander