[erlang-questions] silent death of node

Tony Rogvall tony@REDACTED
Sun Dec 23 12:03:21 CET 2012

I have seen the same in a very similar setup.
I think this may have something to do with a bug in inet_drv.c writev returns 0 for some unknown reason
causing the code looping forever. I think the forever loop was put there to fill the kernel buffer as much
as possible. There exist a patch at erlang-bugs archive somewhere.

Check if this patch works for you.



On 23 dec 2012, at 10:56, Dmitry Kolesnikov <dmkolesnikov@REDACTED> wrote:

> Hello,
> I got an interesting issue of silent death erlang node. I am in the process of investigation what is going on but may be some of you met similar issue.
> So, I am using R15B01 and R15B03-1 on EC2 small instance. The application is trivial it opens tcp/ip socket and periodically dumps a file to it, supervisor is used to manage processes, etc. I am using rebar to package the app andotp runtime. The application is started as expected but after some time it hands up. Both lager and sasl logs are empty, no error, crashes are reported. Any node attach attempts are failed with error 'Node is not running'...
> Any hints on the issue?
> Thank you in advanced and Best Regards, 
> Dmitry
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

"Installing applications can lead to corruption over time. Applications gradually write over each other's libraries, partial upgrades occur, user and system errors happen, and minute changes may be unnoticeable and difficult to fix"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20121223/202fbde9/attachment.htm>

More information about the erlang-questions mailing list