Crash after connection (possible duplicate)

[zachdaniel]

Wanted to lodge a new issue since the other one referencing this (#43) was closed and appears to have been fixed.

I'm getting this same issue. I've updated credo to use runtime: false, I've also removed wobserver from my application (an issue I saw elsewhere) and also I've used the latest binary from the releases page.

** {{timeout,{gen_server,call,
                         [epl_tracer,
                          {command,#Fun<supervisor.which_children.1>,
                                   [<6914.2686.0>]}]}},
    [{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},
     {epl_st,command,2,[{file,"src/epl_st.erl"},{line,129}]},
     {epl_st,generate_sup_tree,1,[{file,"src/epl_st.erl"},{line,104}]},
     {epl_st,'-handle_info/2-fun-0-',2,[{file,"src/epl_st.erl"},{line,76}]},
     {lists,foldl,3,[{file,"lists.erl"},{line,1263}]},
     {epl_st,handle_info,2,[{file,"src/epl_st.erl"},{line,75}]},
     {gen_server,try_dispatch,4,[{file,"gen_server.erl"},{line,601}]},
     {gen_server,handle_msg,5,[{file,"gen_server.erl"},{line,667}]}]}

=INFO REPORT==== 16-Jun-2017::17:23:38 ===
    application: epl_st
    exited: shutdown
    type: temporary

Elixir v 1.4.2 OTP 19

Any thoughts or assistance is greatly appreciated.

[zachdaniel]

I've just tried building master and using that and had the same issue.

[arkgil]

Hi @zachdaniel , thanks for posting the issue! 🙂

Could you please share a list of applications which are started on the node you are observing with erlangpl?

If you're using Elixir, you can use:

iex> :application.info()[:running]

and in case of Erlang:

erl> proplists:get_value(running, application:info()).

This issue usually comes up because of misbehaving OTP applications, but this could be the problem on our side.

And sorry for keeping you waiting 😉

[rickpayne]

I'm seeing the same thing. My application list is:

[{cuttlefish,undefined}, {setup,<0.1363.0>}, {riak_core,<0.970.0>}, {exometer_core,<0.942.0>}, {cowboy,<0.937.0>}, {lager,<0.913.0>}, {cowlib,undefined}, {basho_stats,undefined}, {riak_sysmon,<0.901.0>}, {goldrush,<0.894.0>}, {recon,undefined}, {luerl,<0.880.0>}, {jiffy,undefined}, {ranch,<0.874.0>}, {crypto,undefined}, {compiler,undefined}, {syntax_tools,undefined}, {clique,<0.866.0>}, {poolboy,undefined}, {pbkdf2,undefined}, {eleveldb,undefined}, {sasl,<0.855.0>}, {runtime_tools,<0.850.0>}, {mnesia,<0.834.0>}, {stdlib,undefined}, {kernel,<0.797.0>}]

Edit: Yup, indeed - it is bad otp applications. I have a quick-and-dirty workaround for which I'll submit a pull request...