<div dir="ltr">No, I realized the problem:<br><br>I was preparing my embedded yaws with this:<br>Debug = false,<br>GC = yaws_config:make_default_gconf(Debug, "myserver"),<br><br>In the old yaws-1.87, the above would write logs to tty.<br>
<br>But in the new version yaws-1.98 if you want this, you need to enable debug:<br>Debug = true,<br>GC = yaws_config:make_default_gconf(Debug, "myserver"),<br><div><div class="gmail_extra"><br></div><div class="gmail_extra">
So the change was a correction of inappropriate behaviour for production.<br></div><div class="gmail_extra">Regards,<br>Takeshi<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 9:37 PM, mayamatakeshi <span dir="ltr"><<a href="mailto:mayamatakeshi@gmail.com" target="_blank">mayamatakeshi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Ah, yes. I didn't thought to check that file.<br></div>The ERROR REPORTs (not crash reports, as I mentioned by mistake) are there.<br>
So it just happens that we don't have output to tty anymore.<br>
Thanks.<br><div><div><br></div></div></div><div class=""><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 9:06 AM, Steve Vinoski <span dir="ltr"><<a href="mailto:vinoski@ieee.org" target="_blank">vinoski@ieee.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">You might try checking the report.log file in the logdir directory configured in yaws.conf.<div>
<br></div>
<div>--steve<br><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Tue, Mar 25, 2014 at 7:53 PM, mayamatakeshi <span dir="ltr"><<a href="mailto:mayamatakeshi@gmail.com" target="_blank">mayamatakeshi@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><div dir="ltr"><div>Yes, sasl is running:<br><br><0.58.0> supervisor:sasl/1 233 158 0<br>
sasl_sup gen_server:loop/6 9 <br><0.59.0> supervisor:sasl/1 233 170 0<br>
sasl_safe_sup gen_server:loop/6 9 <br><br></div>However, I tested forcing a crash on a different module (not yaws).<br>And I got this:<br><div><br>=CRASH REPORT==== 26-Mar-2014::08:47:17 ===<br>
crasher:<br> initial call: registrar:init/1<br> pid: <0.156.0><br> registered_name: registrar<br> exception exit: {bad_return_value,tcp_closed}<br> in function gen_server:terminate/6 (gen_server.erl, line 744)<br>
ancestors: [appex_sup,<0.66.0>]<br> messages: []<br> links: [<0.132.0>]<br> dictionary: []<br> trap_exit: false<br> status: running<br> heap_size: 610<br> stack_size: 27<br> reductions: 2308<br>
neighbours:<br><br><div class="gmail_extra">So, sasl crash reporting to tty seems OK.<br>So what seems to be happening is that yaws is somehow inhibiting its crash reports.<br></div><div class="gmail_extra">I will check this.<br>
<br></div><div class="gmail_extra">Regards,<br></div><div class="gmail_extra">Takeshi.<br></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 3:50 AM, Siri Hansen <span dir="ltr"><<a href="mailto:erlangsiri@gmail.com" target="_blank">erlangsiri@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Is the sasl application running on your node?<div>/siri<br><br>tisdagen den 25:e mars 2014 skrev mayamatakeshi <<a href="mailto:mayamatakeshi@gmail.com" target="_blank">mayamatakeshi@gmail.com</a>>:<div>
<div><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div>Hello,<br>I have spend some time updating an old OTP app that was running with<br> Erlang R13B03 and yaws-1.87<br></div>to <br><div> Erlang R16B03-1 and yaws-1.98<br></div><div>The app is working fine, but now starting to code more features and debugging with the new version, I am not seeing sasl writing crash reports to tty anymore.<br>
<br></div><div>The sasl is writing progress and info reports to tty:<br>=PROGRESS REPORT==== 25-Mar-2014::21:38:04 ===<br> supervisor: {local,kernel_safe_sup}<br> started: [{pid,<0.164.0>},<br>
{name,timer_server},<br>
{mfargs,{timer,start_link,[]}},<br> {restart_type,permanent},<br> {shutdown,1000},<br> {child_type,worker}]<br><br>=INFO REPORT==== 25-Mar-2014::21:38:34 ===<br>
Send ping frame<br>=INFO REPORT==== 25-Mar-2014::21:39:04 ===<br>Send ping frame<br>=INFO REPORT==== 25-Mar-2014::21:39:34 ===<br>Send ping frame<br><br></div><div>The above are due a WebSocket connection to yaws.<br><br>
</div><div>I force a crash doing this in yaws:<br></div><div><br>out(A) -><br> X = 1,<br> Y = 2,<br> X = Y,<br>...<br><br>I know the crash is happening because the HTTP request gets this:<br><br># curl -x "" <a href="http://127.0.0.1:12121/dialplan" target="_blank">http://127.0.0.1:12121/dialplan</a><br>
<br><h2>Internal error, yaws code crashed</h2><br /><hr /><br><pre><br><br>ERROR erlang code threw an uncaught exception:<br> File: appmod:0<br>Class: error<br>Exception: {badmatch,false}<br>
Req: {http_request,'GET',{abs_path,"/dialplan"},{1,1}}<br>Stack: [{dialplan,out,1,[{file,"src/dialplan.erl"},{line,19}]},<br> {yaws_server,deliver_dyn_part,8,<br> [{file,"yaws_server.erl"},{line,2801}]},<br>
{yaws_server,aloop,4,[{file,"yaws_server.erl"},{line,1215}]},<br> {yaws_server,acceptor0,2,[{file,"yaws_server.erl"},{line,1052}]},<br> {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]<br>
</pre><hr /><br><br><br></div><div>But still I don't get crash reports in the tty.<br><br></div><div>Does anyone know of any change related to this?<br><br></div><div>Regards,<br></div><div>Takeshi<br></div>
<div></div><div><br><br><br></div></div>
</blockquote></div></div></div>
</blockquote></div><br></div></div></div></div></div>
<br></div></div>_______________________________________________<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>
<br></blockquote></div><br></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div>