myoss opened a new issue #6189: URL: https://github.com/apache/apisix/issues/6189
### Issue description enable zipkin plugin, collecting logs with jaeger-collector-agent, request route failed ### Environment - apisix version (cmd: `apisix version`): 2.11.0-alpine - OS (cmd: `uname -a`): k8s pod - OpenResty / Nginx version (cmd: `nginx -V` or `openresty -V`): - etcd version, if have (cmd: run `curl http://127.0.0.1:9090/v1/server_info` to get the info from server-info API): 3.4.16 - apisix-dashboard version, if have: 2.10.1-alpine - the plugin runner version, if the issue is about a plugin runner (cmd: depended on the kind of runner): - luarocks version, if the issue is about installation (cmd: `luarocks --version`): ### Steps to reproduce 1. enable zipkin in global plugin ``` { "endpoint": "http://jaeger-collector-test.examle.com:9411/api/v2/spans", "sample_ratio": 1, "service_name": "APISIX-IN-SG", "server_addr": "192.168.3.50" } ``` 2. create a route 3. request route failed ### Actual result request route success ### Error log ``` 2022/01/24 08:11:12 [error] 46#46: *54652654 failed to run log_by_lua*: /usr/local/apisix/apisix/plugins/zipkin.lua:273: attempt to index field 'response_span' (a nil value) stack traceback: /usr/local/apisix/apisix/plugins/zipkin.lua:273: in function 'phase_func' /usr/local/apisix/apisix/plugin.lua:743: in function 'run_plugin' /usr/local/apisix/apisix/plugin.lua:776: in function 'run_global_rules' /usr/local/apisix/apisix/init.lua:335: in function 'common_phase' /usr/local/apisix/apisix/init.lua:708: in function 'http_log_phase' log_by_lua(nginx.conf:350):2: in main chunk while logging request, client: 172.20.211.54, server: _, request: "PUT /apisix/admin/global_rules/1 HTTP/1.0", upstream: "http://10.2.167.113:80/apisix/admin/global_rules/1", host: "dashboard-test.example.com", referrer: "https://dashboard-test.example.com/plugin/list" ``` ### Expected result _No response_ -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
