Error with the "mashape-analytics" plugin

[dpanelli]

Hello ,
I'm having this error after activating the plugin:

2015/07/23 13:32:59 [error] 37#0: *110 failed to run log_by_lua*: ...local/share/lua/5.1/kong/plugins/log_serializers/alf.lua:139: bad argument #1 to 'len' (string expected, got nil)
stack traceback:
    [builtin:len]: in function 'len'
    ...local/share/lua/5.1/kong/plugins/log_serializers/alf.lua:139: in function 'serialize_entry'
    ...local/share/lua/5.1/kong/plugins/log_serializers/alf.lua:175: in function 'add_entry'
    ...share/lua/5.1/kong/plugins/mashape-analytics/handler.lua:140: in function 'log'
    /usr/local/share/lua/5.1/kong.lua:254: in function 'exec_plugins_log'
    log_by_lua(nginx.conf:103):1: in function <log_by_lua(nginx.conf:103):1>

Any idea?

I'm using the latest docker image.

[nicksamps]

+1

Here's some of our logs:

2015/07/23 18:53:28 [error] 10032#0: *911285 failed to run log_by_lua*: ...local/share/lua/5.1/kong/plugins/log_serializers/alf.lua:99: attempt to perform arithmetic on field 'upstream_response_time' (a string value)
stack traceback:
    ...local/share/lua/5.1/kong/plugins/log_serializers/alf.lua:99: in function 'serialize_entry'
    ...local/share/lua/5.1/kong/plugins/log_serializers/alf.lua:175: in function 'add_entry'
    ...share/lua/5.1/kong/plugins/mashape-analytics/handler.lua:140: in function 'log'
    /usr/local/share/lua/5.1/kong.lua:254: in function 'exec_plugins_log'
    log_by_lua(nginx.conf:103):1: in function <log_by_lua(nginx.conf:103):1> while logging request, 

2015/07/23 18:53:54 [error] 10032#0: [lua] handler.lua:68: [mashape-analytics] socket refused the batch: , context: ngx.timer, client: 47.19.42.194, server: 0.0.0.0:80
2015/07/23 18:53:54 [error] 10032#0: [lua] handler.lua:68: [mashape-analytics] socket refused the batch: The payload may not exceed 1Mb, context: ngx.timer, client: 162.1.129.32, server: 0.0.0.0:80

[nicksamps]

I'm actually seeing a similar error with file log as well

[error] 10561#0: *6449 failed to run log_by_lua*: ...cal/share/lua/5.1/kong/plugins/log_serializers/basic.lua:22: attempt to perform arithmetic on field 'upstream_response_time' (a nil value)
stack traceback:
    ...cal/share/lua/5.1/kong/plugins/log_serializers/basic.lua:22: in function 'serialize'
    /usr/local/share/lua/5.1/kong/plugins/filelog/log.lua:44: in function 'execute'
    /usr/local/share/lua/5.1/kong/plugins/filelog/handler.lua:12: in function 'log'
    /usr/local/share/lua/5.1/kong.lua:254: in function 'exec_plugins_log'
    log_by_lua(nginx.conf:103):1: in function <log_by_lua(nginx.conf:103):1> while logging request, client: 216.234.104.26, server: _, request: 

Also seeing a bunch of nginx workers dying as well, for example:

2015/07/23 20:03:03 [alert] 10510#0: worker process 10561 exited on signal 11 (core dumped)

[thibaultcha]

#425 addresses both those issues.

• One was related to this nginx directive being enabled by default for upstream requests that timeout, thus resulting in an edge-case not handled by the ALF serializer.
• The other was an issue when log_body was enabled but the request had no body (ex: GET request)

---

The other errors you are seeing @nicksamps is because you have log_body enabled and thus the buffer is considerably bigger than usual. The mashape analytics server doesn't allow payloads bigger than 1Mb, thus refuses the content of your buffer. This edge-case is not handled yet by the plugin, so I would suggest either not logging the bodies (analytics doesn't use them yet anyways) or set a smaller batch_size value so the buffer gets flushed more frequently and contains less data.

[nicksamps]

Got it, thanks @thibaultcha