[erlang-questions] Can't attach to a running release: "No such device or address"
Mon Jun 23 17:08:03 CEST 2014
Have you made sure that the run_erl program is still running?
> ps aux | grep run_erl
This sort of problem would happen if run_erl for some reason exited without
taking the erlang vm with it and not cleaning up the fifos. There should be
a file called run_erl.log in the same directlory where the erlang log files
are, maybe it contains some information about what has happened?
On Mon, Jun 23, 2014 at 3:13 PM, Ivan Uemlianin <ivan@REDACTED> wrote:
> Dear All
> I have an erlang release (packaged using rebar) running on a server. After
> a bit of maintenance and stopping and starting, I notice I can't attach to
> the running release:
> $ ./bin/appnode attach
> No running Erlang on pipe /tmp/path/to/erlang.pipe.123: No such device
> or address
> The pipe directory exists, containing files erlang.pipe.123.r and
> erlang.pipe.123.w. File permissions look ok. I can ping the node. The
> release is running normally.
> I have tried
> $./erts-18.104.22.168/bin/to_erl /tmp/path/to/erlang.pipe.123
> and that has the same result. (the version of erts is quite old).
> I have googled around the interwebs.
> Can anyone suggset some ideas for why this is happening and, mainly, how I
> can attach?
> With thanks and best wishes
> Ivan A. Uemlianin PhD
> Speech Technology Research and Development
> festina lente
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions