azura27 commented on issue #3107:
URL: https://github.com/apache/apisix/issues/3107#issuecomment-750696395


   First thanks for your response, Some issue need to inform: the apisix is 
running in docker selfbuilt, with base image centOS7; and zipkin reporter been 
reconstructed, substitute the http report way in _M.flush with udp report way:
       local sock = ngx_socket_udp()
       sock:settimeout(conf.timeout)
       local ok, err = sock:setpeername(conf.host, conf.port)
       if not ok then
           return nil, "[zipkin-reporter] could not connect to ", conf.host, 
":", conf.port, ": ", err
       end
       local ok, err
       ok, err = sock:send(pending_spans)
       if not ok then
           return nil, "failed to send: " .. err
       end
       ok, err = sock:close()
       if not ok then
           return nil, "failed to close connection from " .. self.host .. ":" 
.. tostring(self.port) .. ": " .. err
       end
   1,the route is: plugins open:zipkin, rewrite, limit-count
      visit :url --resolve 'domain:80:IP' http://domain/temp.htm
   2, error log:
   2020/12/22 17:07:05 [error] 74#0: *2481202 lua entry thread aborted: runtime 
error: /usr/local/apisix/apisix/plugins/zipkin.lua:149: attempt to index field 
'sampler' (a nil value)
   stack traceback:
   coroutine 0:
           /usr/local/apisix/apisix/plugins/zipkin.lua: in function 'phase_func'
           /usr/local/apisix/apisix/init.lua:157: in function 'run_plugin'
           /usr/local/apisix/apisix/init.lua:553: in function 
'http_access_phase'
           access_by_lua(nginx.conf:207):2: in main chunk while sending to 
client, client: 
   
   If it is convenient, please help on test on your official version if this 
could be recurrent. If cannot be recurrent, could you give some advices? Thanks 
a lot~


----------------------------------------------------------------
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