Having had a closer look at this, I think that the error reason from rb is ok. From rb's point of view the problem is actually that it can not read the index file.<div><br></div><div>However, as it is now, the sasl application will</div>
<div><br></div><div>- successfully start, and add the log_mf_h report handler, if all three environment variables are given with valid values</div><div>- successfully start, but not add the log_mf_h report handler, if some or all of the three environment variables are missing</div>
<div>- fail to start if any of the three environment variables are given with an invalid value</div><div><br></div><div>I actually think that the startup of sasl should fail also in the case when some *but not all* of the three environment variables are given. I will correct that.</div>
<div><br></div><div>Regards</div><div>/siri</div><div><br></div><div><br></div><div><br><div class="gmail_quote">2011/4/4 Siri Hansen <span dir="ltr"><<a href="mailto:erlangsiri@gmail.com" target="_blank">erlangsiri@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Gleb - I don't know if you have already sorted this out by yourself - but anyway... You just have an underscore too much in your config file. 'error_logger_mf_max_files' should be 'error_logger_mf_maxfiles'!<div>
<br></div><div>I will have a look at the error reason - I think it should be pointing closer to the real error...</div><div><br></div><div>Regards</div><div>/siri@otp<div><div></div><div><br><div><br><div class="gmail_quote">
2011/3/31 Gleb Peregud <span dir="ltr"><<a href="mailto:gleber.p@gmail.com" target="_blank">gleber.p@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
I'm digging into using rb for log viewing. As far as I understood from<br>
documentation, some blogs and other emails here it is enough to define<br>
the following parameters in the sasl application's config:<br>
<br>
error_logger_mf_dir<br>
error_logger_mf_maxbytes<br>
error_logger_mf_max_files<br>
<br>
Here's an output of my test:<br>
<br>
============================================<br>
gleber@first:~/tmp/test$ ls<br>
rb.config test.sh<br>
<br>
gleber@first:~/tmp/test$ cat rb.config<br>
[<br>
{sasl, [<br>
{error_logger_mf_dir, "."},<br>
{error_logger_mf_maxbytes, 1024},<br>
{error_logger_mf_max_files, 10}<br>
]<br>
}<br>
].<br>
<br>
gleber@first:~/tmp/test$ cat test.sh<br>
#!/bin/sh<br>
<br>
exec erl -sname test \<br>
-config rb \<br>
-boot start_sasl<br>
<br>
gleber@first:~/tmp/test$ ./test.sh<br>
Erlang R14A (erts-5.8) [source] [smp:2:2] [rq:2] [async-threads:0]<br>
[kernel-poll:false]<br>
<br>
<br>
=PROGRESS REPORT==== 31-Mar-2011::20:36:09 ===<br>
supervisor: {local,sasl_safe_sup}<br>
started: [{pid,<0.41.0>},<br>
{name,alarm_handler},<br>
{mfargs,{alarm_handler,start_link,[]}},<br>
{restart_type,permanent},<br>
{shutdown,2000},<br>
{child_type,worker}]<br>
<br>
=PROGRESS REPORT==== 31-Mar-2011::20:36:09 ===<br>
supervisor: {local,sasl_safe_sup}<br>
started: [{pid,<0.42.0>},<br>
{name,overload},<br>
{mfargs,{overload,start_link,[]}},<br>
{restart_type,permanent},<br>
{shutdown,2000},<br>
{child_type,worker}]<br>
<br>
=PROGRESS REPORT==== 31-Mar-2011::20:36:09 ===<br>
supervisor: {local,sasl_sup}<br>
started: [{pid,<0.40.0>},<br>
{name,sasl_safe_sup},<br>
{mfargs,<br>
{supervisor,start_link,<br>
[{local,sasl_safe_sup},sasl,safe]}},<br>
{restart_type,permanent},<br>
{shutdown,infinity},<br>
{child_type,supervisor}]<br>
<br>
=PROGRESS REPORT==== 31-Mar-2011::20:36:09 ===<br>
supervisor: {local,sasl_sup}<br>
started: [{pid,<0.43.0>},<br>
{name,release_handler},<br>
{mfargs,{release_handler,start_link,[]}},<br>
{restart_type,permanent},<br>
{shutdown,2000},<br>
{child_type,worker}]<br>
<br>
=PROGRESS REPORT==== 31-Mar-2011::20:36:09 ===<br>
application: sasl<br>
started_at: test@first<br>
Eshell V5.8 (abort with ^G)<br>
(test@first)1> rb:start().<br>
{error,{"cannot read the index file",<br>
{child,undefined,rb_server,<br>
{rb,start_link,[[]]},<br>
temporary,brutal_kill,worker,<br>
[rb]}}}<br>
(test@first)2><br>
=CRASH REPORT==== 31-Mar-2011::20:36:11 ===<br>
crasher:<br>
initial call: rb:init/1<br>
pid: <0.49.0><br>
registered_name: []<br>
exception exit: "cannot read the index file"<br>
in function gen_server:init_it/6<br>
ancestors: [sasl_sup,<0.38.0>]<br>
messages: []<br>
links: [<0.39.0>]<br>
dictionary: []<br>
trap_exit: true<br>
status: running<br>
heap_size: 233<br>
stack_size: 24<br>
reductions: 266<br>
neighbours:<br>
<br>
(test@first)2> q().<br>
ok<br>
(test@first)3><br>
<br>
gleber@first:~/tmp/test$ ls<br>
rb.config test.sh<br>
============================================<br>
<br>
Am I missing something in the configuration of sasl or is there<br>
anything else I have to do to make sasl attach error_logger_mf_h to<br>
error logger?<br>
<br>
Best,<br>
<font color="#888888">Gleb Peregud<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</font></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>