dunker1304
I used mix release for deployment. After building a new version with mix release , I started the system as a daemon with IEx attached (daemon_iex ). I then checked the process ID of the running system using the pid command and ps aux | grep beam . It returned the same process ID. However, I cannot stop the running system using a remote command (stop ), either remote or restart . Each time a new version is built, I have to kill the process using the sudo kill -9 [pid] command and rerun the daemon_iex command. Can you explain what is happening with my system?
Thanks.
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
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
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.
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)
dominicletz
Hey @dunker1304 just adding here the issues I’m seeing myself most commonly:
When packaging and deploying a release on the server
stopremoterestartrpcwill only work if the hostname of the machine is aliased to 127.0.0.1 – This is my own most common mistake, as root this will fix it:restartdoes not kill the process and does not create a newPIDinstead it calls System.restart() which restarts all elixir applications inside the existingPID. So it’s an internal restart “only”.