Mix phx.server not running for one collaborator in dev

Phoenix Forum Questions / Help
1

I have a collaborator who is unable to start my Phoenix 1.3.0 app in development. They are using the exact same versions of Erlang, Elixir, Phoenix, and node as I am. Using just a blank test app, it starts up just fine for him. All of us are using Macs.

Here is what MIX_DEBUG=1 mix phx.server outputs:

** Running mix loadconfig (inside Myapp.Mixfile)
** Running mix phx.server (inside Myapp.Mixfile)
** Running mix deps.loadpaths (inside Myapp.Mixfile)
** Running mix app.start --no-halt (inside Myapp.Mixfile)
** Running mix loadpaths --no-halt (inside Myapp.Mixfile)
** Running mix archive.check --no-halt (inside Myapp.Mixfile)
** Running mix compile --no-halt (inside Myapp.Mixfile)
** Running mix compile.all --no-halt (inside Myapp.Mixfile)
** Running mix compile.phoenix --no-halt (inside Myapp.Mixfile)
** Running mix compile.gettext --no-halt (inside Myapp.Mixfile)
** Running mix compile.yecc --no-halt (inside Myapp.Mixfile)
** Running mix compile.leex --no-halt (inside Myapp.Mixfile)
** Running mix compile.erlang --no-halt (inside Myapp.Mixfile)
** Running mix compile.elixir --no-halt (inside Myapp.Mixfile)
Compiling 73 files (.ex)
** Running mix compile.xref --no-halt (inside Myapp.Mixfile)
** Running mix xref warnings (inside Myapp.Mixfile)
** Running mix compile.app --no-halt (inside Myapp.Mixfile)
Generated myapp app
** Running mix compile.protocols --no-halt (inside Myapp.Mixfile)

It stops here for my collaborator :arrow_up:

It continues with the following for me and other devs :arrow_down:


** Running mix compile.gettext (inside Myapp.Mixfile)
** Running mix compile.phoenix (inside Myapp.Mixfile)
** Running mix compile.elixir (inside Myapp.Mixfile)
** Running mix compile.protocols (inside Myapp.Mixfile)
Hash: f54923058b3f95723c4f
Version: webpack 1.13.1
Time: 14044ms
     Asset     Size  Chunks             Chunk Names
    app.js  2.73 MB       0  [emitted]  main
js/app.css  17.7 kB       0  [emitted]  main
   [0] multi main 28 bytes {0} [built]
 [339] ./deps/phoenix/priv/static/phoenix.js 43.7 kB {0} [built]
    + 804 hidden modules
** Running mix compile.gettext (inside Myapp.Mixfile)
** Running mix compile.phoenix (inside Myapp.Mixfile)
** Running mix compile.elixir (inside Myapp.Mixfile)
** Running mix compile.protocols (inside Myapp.Mixfile)
** Running mix compile.gettext (inside Myapp.Mixfile)
** Running mix compile.phoenix (inside Myapp.Mixfile)
** Running mix compile.elixir (inside Myapp.Mixfile)
** Running mix compile.protocols (inside Myapp.Mixfile)

I’m having trouble thinking through what else to look for. Any ideas?

2

Are they on Windows? Are the rest of you?

3

All of us are using Macs.

4

Ping :ping_pong:

5

Macs I know almost nothing about, especially about how to debug on them. I use Linux at home and Windows at work (usually SSH’d into Linux). Perhaps a Mac user can help? ^.^;

The only real reason I could think of it not working for them is a hardware issue if it halts at ‘that’ point… If on Windows I’d say disable the AV and telemetry for that location. Maybe just have him wipe it all clean, re-clone, and try again? Next reinstall everything? ^.^;

1 Like
6

I had an issue similar to this a couple days ago (I’m on Mac). Unfortunately I could not reproduce it so I couldn’t send a bug ticket in. Unfortunately killing the _build and deps directories did not fix the issue for me. I had to actually kill the entire project directory and re-write (I hadn’t gotten to commit the project yet). I would kill the folder and try again from a fresh clone.

2 Likes
7

That exceptionally sounds like a hardware or filesystem issue. o.O

8

My guess would be more filesystem. Like I said though, I couldn’t reproduce it. It is rather unfortunate. I was just helping a friend go through the getting started guide. Literally the first section on Agents, we were unable to run mix test. Not sure what happened. Quickly re wrote it from scratch again and it worked fine.

9

Wow. That seems really bizarre. I agree that it is more likely a filesystem issue then.

Thanks so much!

10

We already tried cleaning and cloning it again. I’m hoping it doesn’t come to a reinstall! Thanks.

11

Figured it out. It came down to the other dev not having an updated dev.exs.

1 Like