[erlang-questions] How to diagnose stuck Erlang node

Dennis Novikov dennis.novikov@REDACTED
Mon Nov 28 10:47:36 CET 2011

On Mon, 28 Nov 2011 08:44:42 +0200, Kirill Zaborsky <qrilka@REDACTED>  

> Trying to fins any workaround to this "stuck node" scenario I've upgraded
> to R14B04 and turned on "heart".
> But recently  the node once again stopped responding. And heart did not
> assume it to be stuck although I could not contact it.
> I've tried to to get a crashdump with 'kill -USR1' but it appeared that
> once again crash dump was truncated. Does heart kills "dead" erlang node?
> And the only thing that could be seen from the crash dump that the only
> running process was user_drv (just like in previous times) with program
> counter equal to "user_drv:server_loop/5 + 48". Is it possible to find  
> out
> what exactly does it stands for?

Waiting on receive in that function. And you are observing this on a  
32-bit VM.


More information about the erlang-questions mailing list