derek-zhou
I am seeing this in my log:
...
(stdlib 3.7.1) gen_server.erl:637: :gen_server.try_dispatch/4
(stdlib 3.7.1) gen_server.erl:711: :gen_server.handle_msg/6
(stdlib 3.7.1) proc_lib.erl:249: :proc_lib.init_p_do_apply/3
Last message: {:ssl_closed, {:sslsocket, {:gen_tcp, #Port<0.156>, :tls_connection, :undefined}, [#PID<0.2810.0>, #PID<0.2809.0>]}}
And the process crashed. The process was doing some outbound web api calls with HTTPosion prior to the crash, and I guess it hit some tricky spot. I understand web API can fail, however, why does it fail this way? and am I supposed to catch this?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
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.
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!"
Showing Posts 1 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
al2o3cr
The messages look like the ones in this Hackney bug:
https://github.com/benoitc/hackney/issues/464
I’ve seen these infrequently in production (one per thousands of outgoing HTTP requests) so it’s hard to troubleshoot, but AFAIK they are “leftovers” from previously-used connections and don’t affect operations. To stop them crashing my GenServers, I added a
handle_infothat logged about it and went on with life.