jzhao20230918 commented on issue #11134:
URL: https://github.com/apache/apisix/issues/11134#issuecomment-2054807593

   > The information you provided is insufficient to attempt reproduction of 
this bug
   
   here is a simple version of config:
   apisix:
     node_listen: 9080
     enable_ipv6: false
     enable_control: true
     control:
       ip: "0.0.0.0"
       port: 9092
   deployment:
     admin:
       allow_admin:  
         - 0.0.0.0/0
       admin_key:
         - name: "admin"
           key: edd1c9f034335f136f87ad84b625c8f1
           role: admin
         - name: "viewer"
           key: 4054f7cf07e344346cd3f287985e76a2
           role: viewer
     etcd:
       host:
         - "http://etcd1.internal:2379";
       prefix: "/apisix"
       timeout: 30
   discovery:
     consul:
       servers:
         - "http://consul.internal:8500";
   plugin_attr:
     prometheus:
       export_addr:
         ip: "0.0.0.0"
         port: 9091
   
   
   I got the error after started apisix:
   2024/04/15 03:29:29 [error] 49#49: *40 lua entry thread aborted: runtime 
error: /usr/local/apisix/apisix/discovery/consul/init.lua:525: attempt to 
concatenate local 'svc_port' (a nil value)
   
   I suspect something is wrong here and causes service discovery by consul 
failed.
   stack traceback:
   coroutine 0:
        /usr/local/apisix/apisix/discovery/consul/init.lua: in function 
</usr/local/apisix/apisix/discovery/consul/init.lua:362>, context: ngx.timer
   2024/04/15 03:42:22 [error] 49#49: *7191 [lua] init.lua:91: nodes(): fetch 
nodes failed by ws-http-echo, return default service, client: 10.0.2.59, 
server: _, request: "GET / HTTP/1.1", host: "echo.external.apisix"
   2024/04/15 03:42:22 [error] 49#49: *7191 [lua] init.lua:548: 
handle_upstream(): failed to set upstream: no valid upstream node: nil, client: 
10.0.2.59, server: _, request: "GET / HTTP/1.1", host: "echo.external.apisix"


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

Reply via email to