cowboy_protocol error

[gerep]

I just checked my logs, Poxa is running and working but I see this often, what is it telling me? 😄

02:14:33.906 [error] Error in process #PID<0.1599.1> on node :"poxa@127.0.0.1" with exit value:
{:function_clause,
 [{:cowboy_protocol, :parse_method,
   ["",
    {:state, #Port<0.35795>, :ranch_tcp, [:cowboy_router, :cowboy_handler],
     false,
     [listener: :http,
      dispatch: [{:_, [],
        [{["ping"], [], Poxa.PingHandler, []},
         {["console"], [], Poxa.Console.WSHandler, []},
         {[], [], :cowboy_static, {:priv_file, :poxa, 'index.html'}},
         {["static", :...], [], :cowboy_static, {:priv_dir, :poxa, 'static'}},
         {["apps", :app_id, "events"], [], Poxa.EventHandler, []},
         {["apps", :app_id, "channels"], [], Poxa.ChannelsHandler, []},
         {["apps", :app_id, "channels", :channel_name], [],
          Poxa.ChannelsHandler, []},
         {["apps", :app_id, "channels", :channel_name, "users"], [],
          Poxa.UsersHandler, []},
         {["app", :app_key], [], Poxa.WebsocketHandler, []}]}]], :undefined,
     :undefined, 5, 1, 100, 4096, 64, 4096, 100, 5000, 1448936078905},
    <<1, 100, 101, 102, 97, 117, 108, 116, 10>>],
   [file: 'src/cowboy_protocol.erl', line: 168]}]}


02:14:33.907 [error] Ranch listener :http had connection process started with :cowboy_protocol:start_link/4 at #PID<0.1599.
1> exit with reason: {:function_clause, [{:cowboy_protocol, :parse_method, ["", {:state, #Port<0.35795>, :ranch_tcp, [:cowb
oy_router, :cowboy_handler], false, [listener: :http, dispatch: [{:_, [], [{["ping"], [], Poxa.PingHandler, []}, {["console
"], [], Poxa.Console.WSHandler, []}, {[], [], :cowboy_static, {:priv_file, :poxa, 'index.html'}}, {["static", :...], [], :c
owboy_static, {:priv_dir, :poxa, 'static'}}, {["apps", :app_id, "events"], [], Poxa.EventHandler, []}, {["apps", :app_id, "
channels"], [], Poxa.ChannelsHandler, []}, {["apps", :app_id, "channels", :channel_name], [], Poxa.ChannelsHandler, []}, {[
"apps", :app_id, "channels", :channel_name, "users"], [], Poxa.UsersHandler, []}, {["app", :app_key], [], Poxa.WebsocketHan
dler, []}]}]], :undefined, :undefined, 5, 1, 100, 4096, 64, 4096, 100, 5000, 1448936078905}, <<1, 100, 101, 102, 97, 117, 1
08, 116, 10>>], [file: 'src/cowboy_protocol.erl', line: 168]}]}

[edgurgel]

Thanks for opening the issue. I will take a look soon! :)

[edgurgel]

Well I'm keen to update cowboy/ranch so we can check if this may fix this weird error.

[daande]

I am seeing something similar.

19:08:04.750 [error] Process #PID<0.288.0> raised an exception
** (FunctionClauseError) no function clause matching in :cowboy_protocol.parse_method/3
    (cowboy) src/cowboy_protocol.erl:168: :cowboy_protocol.parse_method("", {:state, #Port<0.6010>, :ranch_tcp, [:cowboy_router, :cowboy_handler], false, [listener: :http, dispatch: [{:_, [], [{["ping"], [], Poxa.PingHandler, []}, {["console"], [], Poxa.Console.WSHandler, []}, {[], [], :cowboy_static, {:priv_file, :poxa, 'index.html'}}, {["static", :...], [], :cowboy_static, {:priv_dir, :poxa, 'static'}}, {["apps", :app_id, "events"], [], Poxa.EventHandler, []}, {["apps", :app_id, "channels"], [], Poxa.ChannelsHandler, []}, {["apps", :app_id, "channels", :channel_name], [], Poxa.ChannelsHandler, []}, {["apps", :app_id, "channels", :channel_name, "users"], [], Poxa.UsersHandler, []}, {["app", :app_key], [], Poxa.WebsocketHandler, []}]}]], :undefined, :undefined, 5, 1, 100, 4096, 64, 4096, 100, 5000, 1450033689749}, <<22, 3, 1, 0, 155, 1, 0, 0, 151, 3, 1, 175, 119, 45, 240, 251, 205, 85, 128, 119, 147, 7, 23, 35, 75, 27, 155, 143, 63, 233, 48, 133, 220, 87, 186, 33, 60, 254, 68, 61, 139, 128, 57, 0, 0, 28, 192, 10, 192, 20, ...>>)

19:08:04.753 [error] Ranch listener :http had connection process started with :cowboy_protocol:start_link/4 at #PID<0.288.0> exit with reason: {:function_clause, [{:cowboy_protocol, :parse_method, ["", {:state, #Port<0.6010>, :ranch_tcp, [:cowboy_router, :cowboy_handler], false, [listener: :http, dispatch: [{:_, [], [{["ping"], [], Poxa.PingHandler, []}, {["console"], [], Poxa.Console.WSHandler, []}, {[], [], :cowboy_static, {:priv_file, :poxa, 'index.html'}}, {["static", :...], [], :cowboy_static, {:priv_dir, :poxa, 'static'}}, {["apps", :app_id, "events"], [], Poxa.EventHandler, []}, {["apps", :app_id, "channels"], [], Poxa.ChannelsHandler, []}, {["apps", :app_id, "channels", :channel_name], [], Poxa.ChannelsHandler, []}, {["apps", :app_id, "channels", :channel_name, "users"], [], Poxa.UsersHandler, []}, {["app", :app_key], [], Poxa.WebsocketHandler, []}]}]], :undefined, :undefined, 5, 1, 100, 4096, 64, 4096, 100, 5000, 1450033689749}, <<22, 3, 1, 0, 155, 1, 0, 0, 151, 3, 1, 175, 119, 45, 240, 251, 205, 85, 128, 119, 147, 7, 23, 35, 75, 27, 155, 143, 63, 233, 48, 133, 220, 87, 186, 33, 60, 254, 68, 61, 139, 128, 57, 0, ...>>], [file: 'src/cowboy_protocol.erl', line: 168]}]}

[edgurgel]

It feels like a faulty client that is sending an HTTP method that is not correctly parsed. I plan to update cowboy and ranch so we can see if this was some bug with our http server. I will release a new version with it soon!

[daande]

Okay thank you!

On Dec 13, 2015, at 7:30 PM, Eduardo Gurgel notifications@github.com wrote:

It feels like a faulty client that is sending an HTTP method that is not correctly parsed. I plan to update cowboy and ranch so we can see if this was some bug with our http server. I will release a new version with it soon!

—
Reply to this email directly or view it on GitHub.

[edgurgel]

Probably related: ninenines/cowboy#448

[edgurgel]

I'm afraid this is just a faulty client that does not send proper HTTP request, but I just released Poxa 0.5.0 updating cowboy and ranch. https://github.com/edgurgel/poxa/releases/tag/v0.5.0

[Dian8]

Similar cowboy_protocol error with poxa from docker image
edgurgel/poxa-automated:latest and pusher/pusher-php-server 3.0.4

[ilijastuden]

Similar error. Our logs are full of it.

Is there any way to track back this error message to the request that's casuing it? Anything that we could use to debug?

[edgurgel]

Cowboy got upgrade. The next version should have fixed a lot of issues. Feel free to reopen if it's still happening