ShaoZeMing commented on issue #3437:
URL: https://github.com/apache/apisix/issues/3437#issuecomment-768818418


   apisix/logs/error.log
   
   ```
   
   2021/01/28 05:52:18 [warn] 49#49: *1 [lua] plugin.lua:206: load_stream(): 
new plugins: {"mqtt-proxy":true}, context: init_worker_by_lua*
   2021/01/28 05:52:18 [warn] 50#50: *2 [lua] plugin.lua:206: load_stream(): 
new plugins: {"mqtt-proxy":true}, context: init_worker_by_lua*
   2021/01/28 05:52:18 [warn] 51#51: *3 [lua] plugin.lua:206: load_stream(): 
new plugins: {"mqtt-proxy":true}, context: init_worker_by_lua*
   2021/01/28 05:52:18 [warn] 52#52: *4 [lua] plugin.lua:206: load_stream(): 
new plugins: {"mqtt-proxy":true}, context: init_worker_by_lua*
   2021/01/28 05:52:18 [warn] 55#55: *5 [lua] plugin.lua:206: load_stream(): 
new plugins: {"mqtt-proxy":true}, context: init_worker_by_lua*
   2021/01/28 05:52:18 [warn] 49#49: *7 [lua] init.lua:288: 
sync_local_conf_to_etcd(): sync local conf to etcd, context: ngx.timer
   2021/01/28 05:52:50 [error] 51#51: *2271 failed to run 
header_filter_by_lua*: /usr/local/apisix/apisix/core/lrucache.lua:159: invalid 
value (nil) at index 1 in table for 'concat'
   stack traceback:
           [C]: in function 'concat'
           /usr/local/apisix/apisix/core/lrucache.lua:159: in function 
'plugin_ctx'
           /usr/local/apisix/apisix/plugins/cors.lua:168: in function 
'phase_func'
           /usr/local/apisix/apisix/init.lua:164: in function 'run_plugin'
           /usr/local/apisix/apisix/init.lua:625: in function 'common_phase'
           /usr/local/apisix/apisix/init.lua:662: in function 
'http_header_filter_phase'
           header_filter_by_lua:2: in main chunk, client: 192.168.0.139, 
server: , request: "GET / HTTP/1.1", host: "192.168.3.130"
   
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to