kayx23 opened a new issue, #495: URL: https://github.com/apache/apisix-docker/issues/495
### Current Behavior Start APISIX v3.5.0 in [Docker](https://hub.docker.com/r/apache/apisix) with: ```bash $ sudo docker run -d \ --name apisix-standalone \ -p 9080:9080 \ -e APISIX_STAND_ALONE=true \ apache/apisix:3.5.0-debian ``` Update `apisix.yaml` in Docker: ```bash $ sudo docker exec apisix-standalone /bin/bash -c "echo ' routes: - id: httpbin uri: /* upstream: nodes: httpbin.org: 1 type: roundrobin #END ' > /usr/local/apisix/conf/apisix.yaml" ``` The change should be in effect without reloading in standalone mode. However, it is not: ```bash $ curl http://127.0.0.1:9080/ip {"error_msg":"404 Route Not Found"} ``` ### Error Logs ```bash sudo docker logs apisix-standalone ``` You see the following logs being generated repeatedly non-stop: ```text 2023/09/06 06:06:10 [error] 33#33: *65 connect() failed (111: Connection refused) while connecting to upstream, client: unix:, server: , request: "POST /v3/kv/range HTTP/1.1", upstream: "http://127.0.0.1:2379/v3/kv/range";, host: "127.0.0.1" 2023/09/06 06:06:10 [warn] 32#32: *63 [lua] v3.lua:245: _request_uri(): invalid response code: 502. Retrying, context: ngx.timer 2023/09/06 06:06:10 [error] 33#33: *65 connect() failed (111: Connection refused) while connecting to upstream, client: unix:, server: , request: "POST /v3/kv/range HTTP/1.1", upstream: "http://127.0.0.1:2379/v3/kv/range";, host: "127.0.0.1" 2023/09/06 06:06:10 [warn] 32#32: *63 [lua] v3.lua:245: _request_uri(): invalid response code: 502. Retrying, context: ngx.timer 2023/09/06 06:06:10 [error] 33#33: *65 connect() failed (111: Connection refused) while connecting to upstream, client: unix:, server: , request: "POST /v3/kv/range HTTP/1.1", upstream: "http://127.0.0.1:2379/v3/kv/range";, host: "127.0.0.1" 2023/09/06 06:06:10 [warn] 32#32: *63 [lua] v3.lua:245: _request_uri(): invalid response code: 502. Retrying, context: ngx.timer 2023/09/06 06:06:10 [error] 33#33: *65 connect() failed (111: Connection refused) while connecting to upstream, client: unix:, server: , request: "POST /v3/kv/range HTTP/1.1", upstream: "http://127.0.0.1:2379/v3/kv/range";, host: "127.0.0.1" 2023/09/06 06:06:10 [error] 33#33: *46 connect() failed (111: Connection refused) while connecting to upstream, client: unix:, server: , request: "POST /v3/kv/range HTTP/1.1", upstream: "http://127.0.0.1:2379/v3/kv/range";, host: "127.0.0.1" 2023/09/06 06:06:10 [error] 32#32: *63 [lua] config_etcd.lua:159: etcd get: invalid response code: 502, context: ngx.timer 2023/09/06 06:06:10 [warn] 36#36: *44 [lua] v3.lua:245: _request_uri(): invalid response code: 502. Retrying, context: ngx.timer 2023/09/06 06:06:10 [error] 33#33: *46 connect() failed (111: Connection refused) while connecting to upstream, client: unix:, server: , request: "POST /v3/kv/range HTTP/1.1", upstream: "http://127.0.0.1:2379/v3/kv/range";, host: "127.0.0.1" 2023/09/06 06:06:10 [warn] 36#36: *44 [lua] v3.lua:245: _request_uri(): invalid response code: 502. Retrying, context: ngx.timer 2023/09/06 06:06:10 [error] 33#33: *46 connect() failed (111: Connection refused) while connecting to upstream, client: unix:, server: , request: "POST /v3/kv/range HTTP/1.1", upstream: "http://127.0.0.1:2379/v3/kv/range";, host: "127.0.0.1" 2023/09/06 06:06:10 [warn] 36#36: *44 [lua] v3.lua:245: _request_uri(): invalid response code: 502. Retrying, context: ngx.timer 2023/09/06 06:06:10 [error] 33#33: *46 connect() failed (111: Connection refused) while connecting to upstream, client: unix:, server: , request: "POST /v3/kv/range HTTP/1.1", upstream: "http://127.0.0.1:2379/v3/kv/range";, host: "127.0.0.1" 2023/09/06 06:06:10 [error] 36#36: *44 [lua] config_etcd.lua:159: etcd get: invalid response code: 502, context: ngx.timer ``` NOTE: This seems to be specific to v3.5.0 in standalone mode. I do not observe the same logging behaviour in v3.5.0 traditional mode or v3.4.0 standalone mode. ### Environment - APISIX version (run `apisix version`): Docker `apache/apisix:3.5.0-debian` -- 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]
