doaortu

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

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.

Where Next?

Popular in Questions Top

RisingFromAshes
I’ve read in another post that it may be possible with a router helper - but I couldn’t find an appropriate one, and tbh, I’m still just ...
New
minhajuddin
I have seen a lot of code which picks the first element from a list using Enum.at(0) instead of List.first. Is there a reason why people ...
New
Brian
What is the proper way to load a module from a file in to IEX? In the python world, doing something like this pretty standard: from ....
New
gshaw
What is the idiomatic way of matching for not nil in Elixir? E.g., First way: defp halt_if_not_signed_in(conn, signed_in_account) when...
New
belgoros
I’m not a pro in using Regex and can’t figure out why the following behaviour happens, especially if we take into account the difference ...
New
stefanluptak
Hello everybody, usually, I use a 29" ultra-wide monitor for VSCode which can easily accomodate explorer (files panel) + file with code ...
New
freewebwithme
Using vs code and installed ElixirLS: support and debugger. And I got an error popped up on start up says Failed to run ‘elixir’ comma...
New

Other popular topics Top

minhajuddin
I have seen a lot of code which picks the first element from a list using Enum.at(0) instead of List.first. Is there a reason why people ...
New
New
hariharasudhan94
I would like to know what is the best IDE for elixir development?
New
lanycrost
Hi everyone! I need implement if…else if…else condition from my elixir code, and anymore of this control flow structures not work proper...
New
AngeloChecked
What learn first? Rust or Elixir Hi Elixir community! I’m here because i want learn a new language. I’m a junior developer and mainly i ...
New
JorisKok
I have a server on AWS, and was running a load test using artillery. When looking at the Phoenix dashboard I see the Ports going to 100% ...
New

We're in Beta

About us Mission Statement