[erlang-questions] How to diagnose stuck Erlang node
Wed Oct 26 10:19:44 CEST 2011
you can force it by:
kill -USR1 $Pid
is your node running in embedded node? can you connect to the shell? are you
able to send rpc calls from other nodes?
On Wed, Oct 26, 2011 at 9:42 AM, Kirill Zaborsky <qrilka@REDACTED> wrote:
> Recently we have found some problems with our Erlang application:
> For some time system works ok (e.g. before today it run with no problems
> for at least 17 days). Then something happens and it "stucks". It does not
> repond to pings, http interface (mochiweb) gives no replies. The only thing
> that can be observed is standard "ALIVE" message sent to stdout every 15
> minutes when there is no output to stdout. Messages from logs show nothing
> special before logging stops.
> The only thing I could do is just kill the emulator. That gives me
> opportunity to restart the system but gives no additional information about
> the roots of the problem.
> On JVM it's possible to get program thread dump (using QUIT signal) is
> there some ways to "manually" force Erlang emulator to produce crash dump
> without using erlang:halt/1?
> Are there some other ways to diagnose this problem which I should take a
> look at?
> Kind regars,
> Kirill Zaborksy
> erlang-questions mailing list
- Ahmed Omar
Follow me on twitter
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions