doaortu
Can we silenced the output of remote node stdout and stderr when called using :rpc:call?
Hi, I’m trying to control and call phoenix module from another project using :rpc:call and I don’t see any trivial way to silenced the stdout output from the called node,
for example, I want to fetch some data from called node using something like this:
res = :rpc:call(SomeConsumerPhoenixProject.Animals, :get_animal!, [a.id])
but it always debug stdout from the called node, something like this:
13:35:06.623 [debug] QUERY OK source="animals" db=1.0ms queue=1.5ms idle=1131.9ms
SELECT a0."id", a0."name", a0."type", a0."inserted_at", a0."updated_at", a0."deleted_at" FROM "animals" AS a0 WHERE (a0."id" = $1) AND (a0."deleted_at" IS NULL) [1]
↳ SomeConsumerPhoenixProject.Animals.get_animal!/1, at: lib/animals.ex:43
13:35:06.637 [debug] QUERY OK source="animals_i18n" db=1.3ms queue=2.4ms idle=1149.2ms
SELECT a0."id", a0."lang", a0."name", a0."type", a0."animal_id", a0."animal_id" FROM "animals_i18n" AS a0 WHERE (a0."animal_id" = $1) ORDER BY a0."animal_id" [1]
↳ :erpc.execute_call/4, at: erpc.erl:1250
13:35:06.691 [debug] QUERY OK source="cages" db=38.1ms queue=1.3ms idle=1163.3ms
INSERT INTO "cages" ("animal_name","animal_type","inserted_at","updated_at") VALUES ($1,$2,$3,$4) RETURNING "id" [1, 1, ~U[2025-07-07 06:35:06Z], ~U[2025-07-07 06:35:06Z]]
↳ :erpc.execute_call/4, at: erpc.erl:1250
13:35:06.696 [debug] QUERY OK source="animals" db=1.2ms queue=2.0ms idle=1208.5ms
SELECT a0."id", a0."name", a0."type", a0."inserted_at", a0."updated_at", a0."deleted_at" FROM "animals" AS a0 WHERE (a0."deleted_at" IS NULL) []
↳ :erpc.execute_call/4, at: erpc.erl:1250
This is printed in the caller node, not on the called node stdout, can we have some way to silence this from the caller node?
I’ve tried to read the rpc docs at rpc — OTP 29.0.2 (kernel 11.0.2) but I found no flag or a way to silence this output.
Thank you in advance, any help would be appreciated
First Post!
LostKobrakai
Forwarding stdout to the calling node is a feature. This is handled through the setting of group leader, which determine where IO is emitted to. I’m not sure there’s any way to disable this besides disabling the source of the IO.
Popular in Questions
Other popular topics
Latest Phoenix Threads
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
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #hex
- #security









