Geek Answers Handbook

How to determine why the Erlang application does not start?

I am trying to run an Erlang application that does not work. All that I see in the shell:

=INFO REPORT==== 7-Jan-2010::17:37:42 ===
    application: ui
    exited: {shutdown,{ui_app,start,[normal,[]]}}
    type: temporary

How can I get Erlang to give me more information about why the application does not start? There is currently no other way out of the shell.

+5
source share
3 answers

You can try running a shell with more logging support:

erl -boot start_sasl

this may lead to more details.

+13
source

(tp/supervisor-pass-on-errors), R16B. , , , , , {shutdown,{ui_app,start,[normal,[]]}}, .

README:

OTP-10490  == stdlib ==

    If a child process fails in its start function, then the
    error reason was earlier only reported as an error report
    from the error_handler, and supervisor:start_link would only
    return {error,shutdown}. This has been changed so the
    supervisor will now return {error,{shutdown,Reason}}, where
    Reason identifies the failing child and its error reason.
    (Thanks to Tomas Pihl)
+2

This is a pain, but the way I do this is the old-fashioned way: write the io format: to the beginning of the application function (i.e. the module code with the application behavior) and work out which line failed: (

Sometimes brute force and ignorance is your only person ...

0
source

More articles:


All Articles