DougReeder
Identify source of log message "Cannot get connection id for node" & debugging approach
In a project where none of the original developers are available, the central component is a Phoenix server named “reticulum” or “ret” for short. The old environment is a Kubernetes server, and I’m porting it to run using docker compose. There’s only one container running the Phoenix server. It’s currently running on elixir 1.16-otp-25 and erlang 25.3, and the dependencies are very old. (Yes, we plan to update both, but we have more acute problems currently.)
In the log, when the app is idle, I’m seeing this message all the time, with no apparent correlation with other log messages, which I don’t see in the log of the version running in Kubernetes:
[error]
** Cannot get connection id for node :ret@reticulum
Grepping the source files for our code and the dependencies doesn’t find anything that can definitely be connected with the log message. JetBrains’ Junie LLM says
the message format `[error] ** Cannot get connection id for node :ret@reticulum` strongly
suggests it's coming from an Erlang process or an Elixir GenServer.
What should I be looking at to track down and deal with what’s happening here?
Marked As Solved
DougReeder
I don’t know that I fully understand what’s going on, but when I changed from “Peerage.Via.Dns” to “Peerage.Via.Udp”, the warning went away. I then changed it back to “Peerage.Via.Dns” and renamed the service from “reticulum” to “ret”, and the warning also went away. :-S
The file in question is
import Config
import_config "prod.exs"
config :peerage, log_results: true, via: Peerage.Via.Dns, dns_name: "foo.bar", app_name: "foo"
config :ret, RetWeb.Router, secure?: false
config :sentry,
environment_name: :turkey,
json_library: Poison,
included_environments: [:turkey],
tags: %{
env: "turkey"
}
so it’s not clear to me where it’s getting the service name “ret” from.
Currently there’s only a single Phoenix node, but there may have been more than one in the original incarnation.
Thanks for your help!
Also Liked
jstimps
The error appears to come from libcluster.
https://github.com/search?q=repo%3Abitwalker%2Flibcluster+cannot+get+connection+id&type=issues
Unfortunately I can’t provide more guidance as I’ve never used this library. I hope this provides a lead for you though.
Edit: for some reason I had to escape the url because the generated link was not displaying the correct issue query. Apologies to the mods.
Popular in Questions
Other popular topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
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
- #api
- #forms
- #metaprogramming
- #security
- #hex
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.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"