[erlang-questions] No crash reports to tty with OTP R16B03-1

mayamatakeshi <>
Wed Mar 26 13:37:59 CET 2014


Ah, yes. I didn't thought to check that file.
The ERROR REPORTs (not crash reports, as I mentioned by mistake) are there.
So it just happens that we don't have output to tty anymore.
Thanks.



On Wed, Mar 26, 2014 at 9:06 AM, Steve Vinoski <> wrote:

> You might try checking the report.log file in the logdir directory
> configured in yaws.conf.
>
> --steve
>
>
> On Tue, Mar 25, 2014 at 7:53 PM, mayamatakeshi <>wrote:
>
>> Yes, sasl is running:
>>
>> <0.58.0>              supervisor:sasl/1                      233
>> 158    0
>> sasl_sup              gen_server:loop/6
>> 9
>> <0.59.0>              supervisor:sasl/1                      233
>> 170    0
>> sasl_safe_sup         gen_server:loop/6
>> 9
>>
>> However, I tested forcing a crash on a different module (not yaws).
>> And I got this:
>>
>> =CRASH REPORT==== 26-Mar-2014::08:47:17 ===
>>   crasher:
>>     initial call: registrar:init/1
>>     pid: <0.156.0>
>>     registered_name: registrar
>>     exception exit: {bad_return_value,tcp_closed}
>>       in function  gen_server:terminate/6 (gen_server.erl, line 744)
>>     ancestors: [appex_sup,<0.66.0>]
>>     messages: []
>>     links: [<0.132.0>]
>>     dictionary: []
>>     trap_exit: false
>>     status: running
>>     heap_size: 610
>>     stack_size: 27
>>     reductions: 2308
>>   neighbours:
>>
>> So, sasl crash reporting to tty seems OK.
>> So what seems to be happening is that yaws is somehow inhibiting its
>> crash reports.
>> I will check this.
>>
>> Regards,
>> Takeshi.
>>
>>
>> On Wed, Mar 26, 2014 at 3:50 AM, Siri Hansen <>wrote:
>>
>>> Is the sasl application running on your node?
>>> /siri
>>>
>>> tisdagen den 25:e mars 2014 skrev mayamatakeshi <
>>> >:
>>>
>>> Hello,
>>>> I have spend some time updating an old OTP app that was running with
>>>>   Erlang R13B03 and yaws-1.87
>>>> to
>>>>   Erlang R16B03-1 and yaws-1.98
>>>> 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.
>>>>
>>>> The sasl is writing progress and info reports to tty:
>>>> =PROGRESS REPORT==== 25-Mar-2014::21:38:04 ===
>>>>           supervisor: {local,kernel_safe_sup}
>>>>              started: [{pid,<0.164.0>},
>>>>                        {name,timer_server},
>>>>                        {mfargs,{timer,start_link,[]}},
>>>>                        {restart_type,permanent},
>>>>                        {shutdown,1000},
>>>>                        {child_type,worker}]
>>>>
>>>> =INFO REPORT==== 25-Mar-2014::21:38:34 ===
>>>> Send ping frame
>>>> =INFO REPORT==== 25-Mar-2014::21:39:04 ===
>>>> Send ping frame
>>>> =INFO REPORT==== 25-Mar-2014::21:39:34 ===
>>>> Send ping frame
>>>>
>>>> The above are due a WebSocket connection to yaws.
>>>>
>>>> I force a crash doing this in yaws:
>>>>
>>>> out(A) ->
>>>>         X = 1,
>>>>         Y = 2,
>>>>         X = Y,
>>>> ...
>>>>
>>>> I know the crash is happening because the HTTP request gets this:
>>>>
>>>> # curl -x "" http://127.0.0.1:12121/dialplan
>>>>
>>>> <h2>Internal error, yaws code crashed</h2><br /><hr />
>>>> <pre>
>>>>
>>>> ERROR erlang code threw an uncaught exception:
>>>>  File: appmod:0
>>>> Class: error
>>>> Exception: {badmatch,false}
>>>> Req: {http_request,'GET',{abs_path,"/dialplan"},{1,1}}
>>>> Stack: [{dialplan,out,1,[{file,"src/dialplan.erl"},{line,19}]},
>>>>         {yaws_server,deliver_dyn_part,8,
>>>>                      [{file,"yaws_server.erl"},{line,2801}]},
>>>>         {yaws_server,aloop,4,[{file,"yaws_server.erl"},{line,1215}]},
>>>>
>>>> {yaws_server,acceptor0,2,[{file,"yaws_server.erl"},{line,1052}]},
>>>>         {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]
>>>> </pre><hr />
>>>>
>>>>
>>>> But still I don't get crash reports in the tty.
>>>>
>>>> Does anyone know of any change related to this?
>>>>
>>>> Regards,
>>>> Takeshi
>>>>
>>>>
>>>>
>>>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> 
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140326/b76bd1fa/attachment.html>


More information about the erlang-questions mailing list