You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2020/08/04 02:08:42 UTC
[GitHub] [apisix] backnero opened a new issue #1984: request help: APISIX and ETCD(@DOCKER) connect success，but error.log always report some
backnero opened a new issue #1984:
URL: https://github.com/apache/apisix/issues/1984
### Issue description
Apisix and ETCD are used in istio deployed on the basis of k8s, and they are located in the same namespace. In addition to finding errors in error.log, the gateway uses other functions normally.
### Environment
* apisix version (cmd: `apisix version`): 1.4.1
* OS:centos
**env: k8s+istio**
```
2020/08/04 09:53:18 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:53:18 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:53:49 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:53:49 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:54:21 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:54:21 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:54:52 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:54:52 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:55:23 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:55:23 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:55:54 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:55:54 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:56:25 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:56:25 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:56:56 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:56:56 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:57:27 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:57:27 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:57:58 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:57:58 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:58:29 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:58:29 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:59:00 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:59:00 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:59:31 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 09:59:31 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 10:00:02 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 10:00:02 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 10:00:33 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 10:00:33 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 10:01:04 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 10:01:04 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 10:01:35 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 10:01:35 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 10:02:06 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
2020/08/04 10:02:06 [error] 49#49: unexpected response for gateway-etcd.default.svc.cluster.local
```
Apisix and ETCD are in the same namespace, and the etcd timeout set in config.yaml is 3s.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [apisix] backnero closed issue #1984: request help: APISIX and ETCD(@DOCKER) connect success，but error.log always report some
Posted by GitBox <gi...@apache.org>.
backnero closed issue #1984:
URL: https://github.com/apache/apisix/issues/1984
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [apisix] membphis commented on issue #1984: request help: APISIX and ETCD(@DOCKER) connect success，but error.log always report some
Posted by GitBox <gi...@apache.org>.
membphis commented on issue #1984:
URL: https://github.com/apache/apisix/issues/1984#issuecomment-668347178
it seems to be a network problem. you need to resolve it by your self. please pay attention to the DNS resolver.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [apisix] membphis commented on issue #1984: request help: APISIX and ETCD(@DOCKER) connect success，but error.log always report some
Posted by GitBox <gi...@apache.org>.
membphis commented on issue #1984:
URL: https://github.com/apache/apisix/issues/1984#issuecomment-668347352
> ```
> 2020/08/04 10:32:24 [error] 48#48: *3431030 [lua] heartbeat.lua:117: failed to report heartbeat information: timeout, context: ngx.timer
> ```
you can ignore this error message.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [apisix] backnero commented on issue #1984: request help: APISIX and ETCD(@DOCKER) connect success，but error.log always report some
Posted by GitBox <gi...@apache.org>.
backnero commented on issue #1984:
URL: https://github.com/apache/apisix/issues/1984#issuecomment-668345590
```
2020/08/04 10:32:24 [error] 48#48: *3431030 [lua] heartbeat.lua:117: failed to report heartbeat information: timeout, context: ngx.timer
```
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [apisix] backnero commented on issue #1984: request help: APISIX and ETCD(@DOCKER) connect success，but error.log always report some
Posted by GitBox <gi...@apache.org>.
backnero commented on issue #1984:
URL: https://github.com/apache/apisix/issues/1984#issuecomment-669739074
thank you
----------------------------------------------------------------
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:
users@infra.apache.org