Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[error] backend port not found: :inotifywait #776

Closed
jhlllnd opened this issue Apr 17, 2015 · 8 comments
Closed

[error] backend port not found: :inotifywait #776

jhlllnd opened this issue Apr 17, 2015 · 8 comments

Comments

@jhlllnd
Copy link

jhlllnd commented Apr 17, 2015

I get the message

[error] backend port not found: :inotifywait

when running mix phoenix.server

I think i am missing something but i can't find something about phoenix and inotify or inotifywait on google or in the docs. Maybe it has something to do with code reloading?

Edit:
I have Elixir 1.0.3 and phoenix 0.11

@josevalim
Copy link
Member

Yes! You need that for live reloading, we need to make the docs/guides better. Install instructions here:

https://github.com/rvoicilas/inotify-tools/wiki

I can improve phoenix_live_reload readme but I am pinging @jeregrine @lancehalvorsen to let them know and figure out if something needs to be done in the guides front.

@jhlllnd
Copy link
Author

jhlllnd commented Apr 17, 2015

Thanks, that was what i needed to know :)

@sanford
Copy link

sanford commented Mar 12, 2016

@josevalim Having just hit the issue on my linux install, seems the inotify instructions should also be on the installation page, not just the overview page, no?

http://www.phoenixframework.org/docs/installation

rudolfb added a commit to rudolfb/ubuntu-xenial-elixir-install-shell-script that referenced this issue May 14, 2016
@twajjo
Copy link

twajjo commented Feb 8, 2018

Ok, that's great; but how do I just turn inotifywait off? What if I don't need it? What if the error shuts down a dockerized phoenix container I am trying to run?

@josevalim
Copy link
Member

@twajjo it shouldn't shutdown a phoenix container and it is used only in development. If you don't want it at all, remove phoenix_live_reload as a dependency and from your endpoint.ex.

@twajjo
Copy link

twajjo commented Feb 8, 2018

Thanks, Jose. I agree that it should not shut down the phoenix container, and it does not if I use a shell entry point and start the server by hand, but (weirdly enough) it does. Still trying to figure out what the issue is.

@josevalim
Copy link
Member

@twajjo are you setting MIX_ENV=prod when building and starting the app?

@twajjo
Copy link

twajjo commented Feb 8, 2018

Yes I am. The issue was a bad Dockerfile example provided by a co-worker. I have resolved the issue, but many thanks for your attention.

And many more thanks for my new favorite language, Jose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants