Monday, December 15, 2008

logging errors with erlang and mochiweb

If you would like to run mochiweb or any erlang application and log messages to disk to review later, all you have to do is create a simple config file and wrote something in it like as follows:

[{sasl, [
%% minimise shell error logging
{sasl_error_logger, false},
%% only report errors
{errlog_type, error},
%% define the parameters of the rotating log
%% the log file directory
%% # bytes per logfile
{error_logger_mf_maxbytes,10485760}, % 10 MB
%% maximum number of
{error_logger_mf_maxfiles, 10}

let's say we call this filename erlang_log.config. The trick here is that we have to create the log directory for erlang and make sure it's writable by the user which runs erlang process.
# mkdir /var/logs/error_logs/
you can also make it world writable if you don't care about who reads it on the server.
# chmod 777 /var/log/error_logs/

now pass the config file as parameter to your erl command (on mochiweb part, you can edit or file).

erl -config erlang_log

when you first run your erlang process or mochiweb, first of all run on your erlang command prompt
to create index files in log directory and load rb module.Here is some useful commands to see log messages created by erlang. The log files in the directory are binary so you cannot simple read them.You have to read them through erlang (rb module).
%% shows log messages index
%% shows given indexed numbered message details
%% re-reads the error log directory index.

1 comment:

Benjamin Nortier said...

Thanks for the info!

I've just tried it, but I would prefer a log file that is plain text, so I'm going to write one based on the CouchDB logger.

P.S. You can also use application:set_env/3 to set the configuration parameters if you don't want to use a config file...