qtheninja
Mix edeliver start production cookie mismatch help
The actual question is in bold/italics the below is just additional information that may help. Still new to elixir so trying to wrap my head around a full app lifecycle.
mix edeliver start production causes an error that says:
Received ‘pang’ from myapp@127.0.0.1!
▸ Possible reasons for this include:
▸ - The cookie is mismatched between us and the target node
▸ - We cannot establish a remote connection to the node
▸ Received ‘pang’ from myapp@127.0.0.1!
▸ Possible reasons for this include:
▸ - The cookie is mismatched between us and the target node
▸ - We cannot establish a remote connection to the node
I’m using:
elixir 1.7
{:edeliver, “~> 1.6”},
{:distillery, “~> 2.0”}
I’m using server: true in /config/prod.esx
thanks to: Phoenix deployed with edelivery not starting - #2 by idi527
Postgres, erlang and elixir are installed on the server. The build, production releases all seem to work (there are files in the folders). I can ssh into the server using my username@ipaddress and I have the ipaddress and username .deliver/config and config/prod.exs (url: [host: “ip”, port:80]
In --debug mode it goes through a lot of killing/checking and sleeping :
-
kill -0 13815
-
kill -0 13813
-
sleep 0.5
I’ve also tried on the server. bin/myapp start
It gives no response back
**So I’m guessing the remote connection is a response to not having the right erlang cookies? **
I haven’t been able to find much details on how to lay out the cookies so they match up. I saw a comment stating that they are autogenerated and you shouldn’t hardcode cookies into the system? Any suggestions, reading or ways to navigate this?
Other sources I’ve found that have helped some:
https://medium.com/@zek/deploy-early-and-often-deploying-phoenix-with-edeliver-and-distillery-part-one-5e91cac8d4bd
Most Liked
njwest
I am experiencing this problem with 2.0.10, Elixir 1.7 on Ubuntu 18.04
After mix edeliver deploy to, mix edeliver start [target] gives me a “pang”, but then when I try to start again, it tells me my server is already up and running…
JorisKok
I followed the docs and got the same :pang response after having my mix.exs like this:
def application, do: [
applications: [:edeliver],
mod: {Ankikorean.Application, []},
extra_applications: [:logger, :runtime_tools]
]
After changing it to the following code it worked.
def application do
[
mod: {Ankikorean.Application, []},
extra_applications: [:logger, :runtime_tools, :edeliver]
]
end
shamanime
You can try hardcoding your PORT and any other environment variable that you need to set.
If the app starts, then you know this was the issue. If it doesn’t, it’s one less thing for you to worry about while you keep testing. You can come back and configure them dynamically later. I just noticed Distillery 2 added a few other ways to configure those (link).
Merff
Set the PORT environment variable helped me.
ecly
Are you still seeing this issue or did you find a solution for your case?
I’ve been experiencing it for several weeks with 2.0.10 not using any system environment variables.
2x Received ‘pang’…, when starting the application after having stopped it. Complete fresh deploy/starts work fine.
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
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.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
Courses that'll move you from confusion to "Aha, now I get it!"