[erlang-questions] Can't attach to a running release: "No such device or address"
Mon Jun 23 16:55:03 CEST 2014
You can always start remshell, even someone attached:
1. erl -name myremnode -setcookie samecookieas1stnode
2. press Ctrl + g (you can put single char 'h' to get help there)
3. User switch command
--> r 'mynodename@REDACTED'
Eshell V5.10.4 (abort with ^G)
if you don't have erlang installed on that machine you could always use
thos, which packaged with release: `find rel_dir -type f -name erl`
On Monday, June 23, 2014 5:13:25 PM UTC+4, Ivan Uemlianin 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