vrod
I am wondering if I am doing this properly – I made another post about this but I deleted it because maybe it was unclear, so this time I will attempt to make the problem clear.
I am running my app inside iex and there are many log messages. I wish to do some inspections and monitoring of processes and GenStage to see how the progress is going. So I thought I could connect to the running iex session from a different terminal window.
In terminal 1, I start like this: iex --sname conn1 -S mix
In terminal 2, I start like this: iex --sname conn2 --remsh conn1@my-computer -S mix
The problem is that I still see all the log messages in terminal 2, so I still cannot do the inspections.
I am very confused with this and I think I must be doing something wrong. In one simple app, this works ok and the log messages do not appear in terminal 2. But in my regular app, both terminal 1 and terminal 2 show the same firehose of log messages. I have tried removing many things from my app but this still happens.
Thank you for any ideas for how to fix this!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
jeremyjh
I don’t see that behaviour in my app; the remsh does not output the log statements. What does your
config :loggerstatement look like in this app?Also I don’t know what the meaning of
-S mixwould be in Terminal 2; I doubt it hurts anything but it is unnecessary since you are connecting to a process that has already executed mix.vrod
Ah! I was very foolish! The
-S mixwas the problem! Somehow in my app that causes log messages to appear in the other terminal.The correct way to do this:
Thank you!