Mix edeliver start production cookie mismatch help

Have the same error.
elixir 1.7
{:edeliver, “~> 1.4.3”},
{:distillery, “~> 2.0”}

Hey @qtheninja and @Merff.

Is is your first deploy? Have you deployed before and now this is happening?

The cookie is saved on rel/config.exs after you run release.init.

If you didn’t change it after you built your release, they should match up.

Please make sure your distillery version is 2.0.3, I had this same issue and all sorts of weird behaviors because distillery 2.0.2 didn’t include some needed files on the release package.

@shamanime hey! Yes, this is first deploy via distillery + edeliver. I did not change cookie. distillery version is 2.0.3, yes.

Ok then, if you didn’t change the cookie you’re probably receiving pang as a response because your application is failing to start.

Have you followed the instructions on the distillery phoenix walkthrough?

Same here.

1st deploy. No cookie changing. and I created a fresh no change phoenix app and used 2.0.3. Same problem.

I used this article for some guidance: https://medium.com/@zek/deploy-early-and-often-deploying-phoenix-with-edeliver-and-distillery-part-two-f361ef36aa10

As it wasn’t a 100% clear where with the distillery walkthrough to do some of these things (production server, local) but overall it looks pretty close to the walkthrough.

It looks on the server it is failing to start on the server. @shamanime not sure if you have any further suggestions at all.

I can do “PORT=4000 …builds/prod/so_on_and_so_on/bin/myapp foreground”

and it works. If I use “start” instead of foreground it just quietly fails as I cannot view the myIP:4000 site unless I hit foreground again.

I attempted to use foreground again out of curiosity and got this error.
Protocol ‘inet_tcp’: the name myApp@127.0.0.1 seems to be in use by another Erlang node

SO. It must have been running but not being up fully?

@Merff this may help you. I had to go into the “BUILD_AT” link and then keep diving until you get to bin. So I set it up as something like: PORT=4001 /tmp/edeliver/myapp/builds/_build/prod/rel/myapp/bin/myapp foreground

I’m not sure if this will help you at all.

I updated several projects to distillery > 2 and edeliver 1.6. Only one project has the issues as described above. The process of starting or stopping the application do work eventually, but only after outputting several times the Received ‘pang’ from myapp@127.0.0.1! line.

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).

Set the PORT environment variable helped me.

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.