dunker1304
Mix Release remote, stop, restart command are not working
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.
Most Liked
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:sudo su echo 127.0.0.1 $(hostname) >> /etc/hosts -
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”.
Popular in Questions
Other popular topics
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
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance








