smanza
Hello.
I’m currently facing some issue with hot upgrade using Distillery.
After generating the release as upgrade MIX_ENV=prod mix distillery.release --upgrade
I triggered the upgrade on the running release /opt/app/bin/my_app upgrade
I got this error from the release handler
release_handler:install_release(Vsn="0.12.0" Opts=[{update_paths,true}]) failed, Reason={'EXIT', {timeout, {sys,get_status,[<0.2609.0>]}}}
And the whole VM crashed.
Did you already face this kind of issue ?
How I can know which process it’s ?
Am I missing something in the relup ?
Thanks by advance
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
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 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ruslandoga
If you have access to crash dump, you might find that process there:
Also, is there any other info in the error message, like a stacktrace?
smanza
No, unfortunately. I saw a similar post on Erlang pipermail but without solution.
I will try to look at the crash dump.
smanza
In fact, there was no crash dump, but the entire application’s supervision tree restarted after this error
smanza
I found out this error:
release_handler: cannot find top supervisor for application :bunt.This seems related to this (Error during upgrade: cannot find top supervisor for application <x>? · Issue #183 · bitwalker/exrm · GitHub)