tellesleandro
I have the following code running on node “a”:
defmodule Devices.Teste do
use GenServer
def start_link() do
IO.inspect(["a", self()])
GenServer.start_link(__MODULE__, [], [])
end
def a(pid) do
IO.inspect(["b", self(), pid])
GenServer.call(pid, :a)
end
@impl true
def init([]) do
IO.inspect(["c", self()])
{:ok, []}
end
@impl true
def handle_call(:a, from, state) do
IO.inspect(["d", :a, self(), from])
Process.sleep(3000)
{:reply, :xyz, state}
end
@impl true
def handle_info(x, state) do
IO.inspect(["e", x, self()])
{:noreply, state}
end
end
From a node b, I call
{:ok, pid} = :erpc.call(:"a@192.168.15.83", Devices.Teste, :start_link, [])
then, the messages
["a", #PID<0.225.0>]
["c", #PID<0.226.0>]
are printed and the call returns
{:ok, #PID<20968.226.0>}
After that, I call
:erpc.call(:"a@192.168.15.83", Devices.Teste, :a, [pid])
then, the message
["b", #PID<0.227.0>, #PID<0.226.0>]
is printed, but I get the following error:
** (exit) {:exception, {:noproc, {GenServer, :call, [#PID<20968.226.0>, :a, 5000]}}}
(kernel 8.5.4) erpc.erl:700: :erpc.call/5
iex:2: (file)
If I call
GenServer.call(pid, :a)
no messages are printed and I get the following error
** (exit) exited in: GenServer.call(#PID<20968.214.0>, :a, 5000)
** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
(elixir 1.15.0) lib/gen_server.ex:1074: GenServer.call/3
iex:2: (file)
What am I missing?
As long as I understand, I should use the “remote” pid that I get from the start_link function.
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
I’ve followed the Phoenix LiveView file upload code here Uploads — Phoenix LiveView v1.0.0-rc.7 and so far everything works just fine wit...
New
I’m using an Umbrella project for a Phoenix application, and I want to have one Ecto Repo and one PostgreSQL database shared by all apps....
New
Hello,
I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter).
The diffic...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #ai
- #iex
- #graphql
- #elixirconf-us
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
anuaralfetahe
When the
:erpccall is finished the spawned process on the remote node is terminated and it brings down the started child as well because they are linked.Consider using
startinstead ofstart_link, and this approach should resolve the issue. Unlikestart_link,startdoes not link the caller to the created processes. As a result, even after the caller terminates, the created processes remain active.There might be a more elegant solution to your problem, but I’m not fully aware of the entire context.
Be careful with ‘start’ because it can leave rogue processes in the system..
tellesleandro
startdid the trick. Thanks @anuaralfetahe.