Phoenix Chat Example crashes on REMOTE only when Phoenix 1.4 and Jason

niccolox · June 13, 2018, 12:16am

I have been struggling with a strange issue(bug?) with Phoenix 1.4 and channels.

It only occurs (I think) when accessing the server from a remote connection.

i.e. When using a macbook or Ubuntu workstation deskop in DEV mode locally I dont see the error.

When I deploy to a remote, cloud vm, i.e. Linode, and run in DEV or PROD mode, I get the error.

My main/original project was working with Phoenix 1.4 (master) on PROD Linode maybe 6 to 8 weeks ago, but now it only runs in local mode.

I replicated the issue/bug with Chris Mccords canonicalish Phoenix Chat Example.

I posted the issue

github.com/chrismccord/phoenix_chat_example

Phoenix 1.4 (master) and Jason gives (ArgumentError) argument error Chat.Endpoint.HTTP (cowboy_protocol) terminated on SINGLE CORE CPU

opened 12:05AM - 13 Jun 18 UTC

closed 02:57AM - 13 Jun 18 UTC

niccolox

I found this bug/error/issue on another project which I am trying to upgrade to …Phoenix 1.4 (master actually) and Jason. In fact, I had been running in production with Phoenix 1.4 (master) and channels where working, but, then it broke. I know, risk of chasing HEAD <> I managed to replicate it I think, using a fork of this project and I would be curious on how to update code etc to bypass. The fork is https://github.com/devekkoio/phoenix_chat_example the error is hard to catch as it only happens on DEV or PROD ( I think ) on a remote connection i.e. it doesnt show up on local dev macbook, or even an Ubuntu workstation, but when pushed to Linode it fails. Havent tried other clouds, but have rebuilt on Linode using Xenial and Bionic, same issue. the error on cowboy 1 is below, there is also a cowboy 2 error which I will skip for now ``` [error] Ranch protocol #PID<0.386.0> of listener Chat.Endpoint.HTTP (cowboy_protocol) terminated ** (exit) exited in: Phoenix.Endpoint.CowboyWebSocket.resume() ** (EXIT) an exception was raised: ** (ArgumentError) argument error :erlang.phash2({#PID<0.386.0>, #Reference<0.412873586.60293121.193514>}, 0) (phoenix) lib/phoenix/socket/pool_supervisor.ex:11: Phoenix.Socket.PoolSupervisor.start_child/3 (phoenix) lib/phoenix/channel/server.ex:45: anonymous fn/3 in Phoenix.Channel.Server.join/4 (chat) lib/chat/endpoint.ex:1: Chat.Endpoint.instrument/4 (phoenix) lib/phoenix/socket.ex:590: Phoenix.Socket.handle_in/4 (phoenix) lib/phoenix/endpoint/cowboy_websocket.ex:84: Phoenix.Endpoint.CowboyWebSocket.websocket_handle/3 (cowboy) /var/www/phx_chat_14/deps/cowboy/src/cowboy_websocket.erl:588: :cowboy_websocket.handler_call/7 (phoenix) lib/phoenix/endpoint/cowboy_websocket.ex:54: Phoenix.Endpoint.CowboyWebSocket.resume/3 [error] Ranch protocol #PID<0.388.0> of listener Chat.Endpoint.HTTP (cowboy_protocol) terminated ** (exit) exited in: Phoenix.Endpoint.CowboyWebSocket.resume() ** (EXIT) an exception was raised: ** (ArgumentError) argument error :erlang.phash2({#PID<0.388.0>, #Reference<0.412873586.60293121.194098>}, 0) (phoenix) lib/phoenix/socket/pool_supervisor.ex:11: Phoenix.Socket.PoolSupervisor.start_child/3 (phoenix) lib/phoenix/channel/server.ex:45: anonymous fn/3 in Phoenix.Channel.Server.join/4 (chat) lib/chat/endpoint.ex:1: Chat.Endpoint.instrument/4 (phoenix) lib/phoenix/socket.ex:590: Phoenix.Socket.handle_in/4 (phoenix) lib/phoenix/endpoint/cowboy_websocket.ex:84: Phoenix.Endpoint.CowboyWebSocket.websocket_handle/3 (cowboy) /var/www/phx_chat_14/deps/cowboy/src/cowboy_websocket.erl:588: :cowboy_websocket.handler_call/7 (phoenix) lib/phoenix/endpoint/cowboy_websocket.ex:54: Phoenix.Endpoint.CowboyWebSocket.resume/3 ```

and the forked Phoenix Chat Example code is

apologies if I have missed something super obvious

benwilson512 · June 13, 2018, 12:29am

I’m not entirely sure it makes sense to duplicate the discussion on both the issue tracker and the forum.

niccolox · June 13, 2018, 6:04am

fair point, its a core bug

niccolox · June 13, 2018, 6:05am

and the way I fixed it was upgrade the VM to a 2 cpu core

its a bug in single core cpu right now on 1.4 dev

niccolox · June 14, 2018, 2:18am

bug fixed https://github.com/phoenixframework/phoenix/issues/2908

I didnt expect this was a core bug, apologies for cross posting