Ben0625 opened a new issue #2919:
URL: https://github.com/apache/apisix/issues/2919
### Issue description
Once I start apisix, the error log keeps flushing the following error
information periodically without stopping:
2020/12/02 10:43:42 [error] 31184#31184: *584 [lua] config_etcd.lua:428:
failed to fetch data from etcd: failed to watch data, response code: 404, etcd
key: /apisix/proto, context: ngx.timer
2020/12/02 10:43:42 [error] 31181#31181: *660 [lua] config_etcd.lua:428:
failed to fetch data from etcd: failed to watch data, response code: 404, etcd
key: /apisix/ssl, context: ngx.timer
2020/12/02 10:43:42 [error] 31181#31181: *682 [lua] config_etcd.lua:428:
failed to fetch data from etcd: failed to watch data, response code: 404, etcd
key: /apisix/consumers, context: ngx.timer
2020/12/02 10:43:42 [error] 31181#31181: *662 [lua] config_etcd.lua:428:
failed to fetch data from etcd: failed to watch data, response code: 404, etcd
key: /apisix/global_rules, context: ngx.timer
2020/12/02 10:43:42 [error] 31180#31180: *698 [lua] config_etcd.lua:428:
failed to fetch data from etcd: failed to watch data, response code: 404, etcd
key: /apisix/services, context: ngx.timer
2020/12/02 10:43:42 [error] 31180#31180: *726 [lua] config_etcd.lua:428:
failed to fetch data from etcd: failed to watch data, response code: 404, etcd
key: /apisix/upstreams, context: ngx.timer
2020/12/02 10:43:42 [error] 31180#31180: *714 [lua] config_etcd.lua:428:
failed to fetch data from etcd: failed to watch data, response code: 404, etcd
key: /apisix/consumers, context: ngx.timer
......
### Environment
* apisix version (cmd: `apisix version`): 2.0
* OS: Centos7
* etcd cluster version:
$ ./etcd --version
etcd Version: 3.4.13
Git SHA: ae9734ed2
Go Version: go1.12.17
Go OS/Arch: linux/amd64
### What's the actual result? (including assertion message & call stack if
applicable)
Strangely, the etcd cluster is running well and so does apisix:
**etcd configuration in config.yaml of apisix:**
etcd:
host:
- "http://10.193.161.151:2389";
- "http://10.193.161.153:2389";
- "http://10.193.161.156:2389";
**One of the yaml files to start etcd cluster:**
name: etcd-161-151-noauth
data-dir: /home/nlu/etcd/data2-noauth
listen-client-urls: http://10.193.161.151:2389,http://127.0.0.1:2389
advertise-client-urls: http://10.193.161.151:2389,http://127.0.0.1:2389
listen-peer-urls: http://10.193.161.151:2390
initial-advertise-peer-urls: http://10.193.161.151:2390
initial-cluster:
etcd-161-153-noauth=http://10.193.161.153:2390,etcd-161-156-noauth=http://10.193.161.156:2390,etcd-161-151-noauth=http://10.193.161.151:2390
initial-cluster-token: etcd-cluster-token-3
initial-cluster-state: new
enable-grpc-gateway: true
logger: zap
**Keys in etcd cluster:**
/apisix/consumers/
init_dir
/apisix/global_rules/
init_dir
/apisix/node_status/
init_dir
/apisix/plugin_metadata/
init_dir
/apisix/plugins/
init_dir
/apisix/proto/
init_dir
/apisix/routes/
init_dir
/apisix/routes/330835041972126084
{"id":"330835041972126084","create_time":1606722651,"update_time":1606806589,"uris":["/test"],"name":"test","methods":["GET","HEAD","POST","PUT","DELETE","OPTIONS","PATCH"],"vars":[],"upstream_id":"330834478979088772"}
/apisix/services/
init_dir
/apisix/ssl/
init_dir
/apisix/stream_routes/
init_dir
/apisix/upstreams/
init_dir
/apisix/upstreams/330834478979088772
{"id":"330834478979088772","create_time":1606722315,"update_time":1606806983,"nodes":[{"host":"10.102.136.44","port":6666,"weight":1},{"host":"10.102.136.44","port":6667,"weight":1}],"timeout":{"connect":6000,"read":6000,"send":6000},"type":"roundrobin","checks":{"active":{"healthy":{"interval":1,"successes":1},"host":"l","http_path":"/","timeout":1,"unhealthy":{"http_failures":1,"interval":1}},"passive":{"healthy":{"successes":1},"unhealthy":{"http_failures":1,"tcp_failures":1}}},"name":"test"}
I create a route with limit-count plugin and it works fine.
### What's the expected result?
No error information in error.log
----------------------------------------------------------------
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]
