Trouble with OTP

View: New views
3 Messages — Rating Filter:   Alert me  

Trouble with OTP

by Tom Ayerst-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I am running Kevin Smith's Mochiweb OTP example (http://weblog.hypotheticalabs.com/?p=226) but I cannot get it to start.  Could anyone give me some hints on interpreting the error messages?  I am running it on Windows.  I am not very familiar with debugging OTP yet.

Thanks

Tom

$ erl -boot file_server-1

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
          supervisor: {local,sasl_safe_sup}
             started: [{pid,<0.32.0>},
                       {name,alarm_handler},
                       {mfa,{alarm_handler,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
          supervisor: {local,sasl_safe_sup}
             started: [{pid,<0.33.0>},
                       {name,overload},
                       {mfa,{overload,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
          supervisor: {local,sasl_sup}
             started: [{pid,<0.31.0>},
                       {name,sasl_safe_sup},
                       {mfa,
                           {supervisor,start_link,
                               [{local,sasl_safe_sup},sasl,safe]}},
                       {restart_type,permanent},
                       {shutdown,infinity},
                       {child_type,supervisor}]

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
          supervisor: {local,sasl_sup}
             started: [{pid,<0.34.0>},
                       {name,release_handler},
                       {mfa,{release_handler,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
         application: sasl
          started_at: nonode@nohost

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
         application: sasl
          started_at: nonode@nohost

=CRASH REPORT==== 4-Jul-2008::20:07:13 ===
  crasher:
    pid: <0.37.0>
    registered_name: []
    exception exit: {bad_return,
                        {{mime_typer_app,start,[normal,[]]},
                         {'EXIT',
                             {undef,
                                 [{mime_typer_app,start,[normal,[]]},
                                  {application_master,start_it_old,4}]}}}}
      in function  application_master:init/4
    initial call: application_master:init(<0.5.0>,<0.36.0>,
                                          {appl_data,mime_typer,
                                           [mime_typer],
                                           undefined,
                                           {mime_typer_app,[]},
                                           [mime_typer,mime_typer_app],
                                           [],infinity,infinity},
                                          normal)
    ancestors: [<0.36.0>]
    messages: [{'EXIT',<0.38.0>,normal}]
    links: [<0.36.0>,<0.5.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 377
    stack_size: 23
    reductions: 88
  neighbours:

=INFO REPORT==== 4-Jul-2008::20:07:13 ===
    application: mime_typer
    exited: {bad_return,
                {{mime_typer_app,start,[normal,[]]},
                 {'EXIT',
                     {undef,
                         [{mime_typer_app,start,[normal,[]]},
                          {application_master,start_it_old,4}]}}}}
    type: permanent
{"Kernel pid terminated",application_controller,"{application_start_failure,mime_typer,{bad_return,{{mime_typer_app,start,[normal,[]]},{'EXIT',{undef,[{mime_typer_app,start,[normal,[]]},{application_master,start_it_old,4}]}}}}}"}

Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,mime_typer,{bad_return,{{mime_typer_app,start,[normal,[]]},{'EXIT',{undef,[{mime_typer_app,start,[normal,[]]},{application_



_______________________________________________
erlang-questions mailing list
erlang-questions@...
http://www.erlang.org/mailman/listinfo/erlang-questions

Re: Trouble with OTP

by Pablo Polvorin :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Tom,

{'EXIT',
                     {undef,
                         [{mime_typer_app,start,[normal,[]]}

looks like the interpreter can't  find that function  (mime_type_app:start/2 ).
The function is defined in the source, so probably your code path is wrong and doesn't include the .beam files that
you have compiled.
try with       
erl -pa DIR
where DIR is the directory where your compiled .beam files reside.

hope this helps



2008/7/4 Tom Ayerst <tom.ayerst@...>:
Hi,

I am running Kevin Smith's Mochiweb OTP example (http://weblog.hypotheticalabs.com/?p=226) but I cannot get it to start.  Could anyone give me some hints on interpreting the error messages?  I am running it on Windows.  I am not very familiar with debugging OTP yet.

Thanks

Tom

$ erl -boot file_server-1

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
          supervisor: {local,sasl_safe_sup}
             started: [{pid,<0.32.0>},
                       {name,alarm_handler},
                       {mfa,{alarm_handler,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
          supervisor: {local,sasl_safe_sup}
             started: [{pid,<0.33.0>},
                       {name,overload},
                       {mfa,{overload,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
          supervisor: {local,sasl_sup}
             started: [{pid,<0.31.0>},
                       {name,sasl_safe_sup},
                       {mfa,
                           {supervisor,start_link,
                               [{local,sasl_safe_sup},sasl,safe]}},
                       {restart_type,permanent},
                       {shutdown,infinity},
                       {child_type,supervisor}]

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
          supervisor: {local,sasl_sup}
             started: [{pid,<0.34.0>},
                       {name,release_handler},
                       {mfa,{release_handler,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
         application: sasl
          started_at: nonode@nohost

=PROGRESS REPORT==== 4-Jul-2008::20:07:13 ===
         application: sasl
          started_at: nonode@nohost

=CRASH REPORT==== 4-Jul-2008::20:07:13 ===
  crasher:
    pid: <0.37.0>
    registered_name: []
    exception exit: {bad_return,
                        {{mime_typer_app,start,[normal,[]]},
                         {'EXIT',
                             {undef,
                                 [{mime_typer_app,start,[normal,[]]},
                                  {application_master,start_it_old,4}]}}}}
      in function  application_master:init/4
    initial call: application_master:init(<0.5.0>,<0.36.0>,
                                          {appl_data,mime_typer,
                                           [mime_typer],
                                           undefined,
                                           {mime_typer_app,[]},
                                           [mime_typer,mime_typer_app],
                                           [],infinity,infinity},
                                          normal)
    ancestors: [<0.36.0>]
    messages: [{'EXIT',<0.38.0>,normal}]
    links: [<0.36.0>,<0.5.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 377
    stack_size: 23
    reductions: 88
  neighbours:

=INFO REPORT==== 4-Jul-2008::20:07:13 ===
    application: mime_typer
    exited: {bad_return,
                {{mime_typer_app,start,[normal,[]]},
                 {'EXIT',
                     {undef,
                         [{mime_typer_app,start,[normal,[]]},
                          {application_master,start_it_old,4}]}}}}
    type: permanent
{"Kernel pid terminated",application_controller,"{application_start_failure,mime_typer,{bad_return,{{mime_typer_app,start,[normal,[]]},{'EXIT',{undef,[{mime_typer_app,start,[normal,[]]},{application_master,start_it_old,4}]}}}}}"}

Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,mime_typer,{bad_return,{{mime_typer_app,start,[normal,[]]},{'EXIT',{undef,[{mime_typer_app,start,[normal,[]]},{application_



_______________________________________________
erlang-questions mailing list
erlang-questions@...
http://www.erlang.org/mailman/listinfo/erlang-questions



--
--
pablo
http://ppolv.wordpress.com
----
_______________________________________________
erlang-questions mailing list
erlang-questions@...
http://www.erlang.org/mailman/listinfo/erlang-questions

Re: Trouble with OTP

by Matthias Lang :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Friday, July 04, Tom Ayerst wrote:

> I am running Kevin Smith's Mochiweb OTP example (
> http://weblog.hypotheticalabs.com/?p=226) but I cannot get it to start.
> Could anyone give me some hints on interpreting the error messages?  I am
> running it on Windows.  I am not very familiar with debugging OTP yet.

I know nothing about mochiweb specifically, but

>                          {'EXIT',
>                              {undef,
>                                  [{mime_typer_app,start,[normal,[]]},
>                                   {application_master,start_it_old,4}]}}}}

this means that the function mime_typer_app:start(normal, []) couldn't
be called.

Without knowing anything about your level of experience, my
stab-in-the-dark guess would be that you haven't compiled the code.

Another likely reason would be a broken code path. Try

  code:get_path().

A less likely but possible reason is that you can't compile the code
because of a broken or outdated erlang install.

Matt
_______________________________________________
erlang-questions mailing list
erlang-questions@...
http://www.erlang.org/mailman/listinfo/erlang-questions
LightInTheBox - Buy quality products at wholesale price