Transport loopywriter run returning connection error desc transport is closing

[Envoy (Epoch 0)] [2020-11-30 07:45:54.938][26][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:54] Unable to establish new stream
2020-11-30T07:45:55.382650Z     info    sds     node:router~172.18.40.10~istio-ingressgateway-76d59b8f49-qsvp6.istio-system~istio-system.svc.cluster.local-1 resource:ROOTCA new connection
2020-11-30T07:45:55.382679Z     info    sds     node:router~172.18.40.10~istio-ingressgateway-76d59b8f49-qsvp6.istio-system~istio-system.svc.cluster.local-2 resource:default new connection
2020-11-30T07:45:55.558572Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 1 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2020-11-30T07:45:55.770409Z     info    cache   Root cert has changed, start rotating root cert for SDS clients
2020-11-30T07:45:55.770676Z     info    sds     node:router~172.18.40.10~istio-ingressgateway-76d59b8f49-qsvp6.istio-system~istio-system.svc.cluster.local-2 resource:default pushed key/cert pair to proxy
2020-11-30T07:45:55.770711Z     info    sds     node:router~172.18.40.10~istio-ingressgateway-76d59b8f49-qsvp6.istio-system~istio-system.svc.cluster.local-2 resource:default pushed secret
2020-11-30T07:45:55.783291Z     info    sds     node:router~172.18.40.10~istio-ingressgateway-76d59b8f49-qsvp6.istio-system~istio-system.svc.cluster.local-1 resource:ROOTCA pushed root cert to proxy
2020-11-30T07:45:55.783317Z     info    sds     node:router~172.18.40.10~istio-ingressgateway-76d59b8f49-qsvp6.istio-system~istio-system.svc.cluster.local-1 resource:ROOTCA pushed secret
2020-11-30T07:45:57.560354Z     info    Envoy proxy is ready
[Envoy (Epoch 0)] [2020-11-30 08:15:51.977][26][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:91] gRPC config stream closed: 13,
2020-11-30T08:16:39.176830Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2020-11-30T08:16:39.176923Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {CONNECTING <nil>}
2020-11-30T08:16:39.182270Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {READY <nil>}
[Envoy (Epoch 0)] [2020-11-30 08:46:20.185][26][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:91] gRPC config stream closed: 13,
2020-11-30T08:48:05.413973Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2020-11-30T08:48:05.414033Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {CONNECTING <nil>}
2020-11-30T08:48:05.419261Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {READY <nil>}
2020-11-30T09:17:55.718346Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2020-11-30T09:17:55.718396Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {CONNECTING <nil>}
2020-11-30T09:17:55.724485Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {READY <nil>}
[Envoy (Epoch 0)] [2020-11-30 09:18:36.376][26][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:91] gRPC config stream closed: 13,
2020-11-30T09:48:51.632720Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2020-11-30T09:48:51.632852Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {CONNECTING <nil>}
2020-11-30T09:48:51.638595Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {READY <nil>}
[Envoy (Epoch 0)] [2020-11-30 09:50:48.693][26][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:91] gRPC config stream closed: 13,
2020-11-30T10:20:10.098491Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2020-11-30T10:20:10.098549Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {CONNECTING <nil>}
2020-11-30T10:20:10.103931Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {READY <nil>}
[Envoy (Epoch 0)] [2020-11-30 10:23:30.186][26][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:91] gRPC config stream closed: 13,
2020-11-30T10:52:25.858932Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2020-11-30T10:52:25.858992Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {CONNECTING <nil>}
2020-11-30T10:52:25.864645Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc00031df70, {READY <nil>}
[Envoy (Epoch 0)] [2020-11-30 10:54:42.187][26][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:91] gRPC config stream closed: 13,
[Envoy (Epoch 0)] [2020-11-30 11:23:47.335][26][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:91] gRPC config stream closed: 13,

Client Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.6-beta.0", GitCommit:"e7f962ba86f4ce7033828210ca3556393c377bcc", GitTreeState:"clean", BuildDate:"2020-01-15T08:26:26Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.11", GitCommit:"3a3612132641768edd7f7e73d07772225817f630", GitTreeState:"clean", BuildDate:"2020-09-02T06:46:33Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  namespace: istio-system
  name: istiocontrolplane
spec:
  profile: default
  components:
    pilot:
      k8s:
        resources:
          requests:
            cpu: 500m
            memory: 2048Mi
          limits:
            cpu: 2000m
            memory: 2048Mi
    base:
      enabled: true
    telemetry:
      enabled: true
      k8s:
        resources:
          requests:
            cpu: 500m
            memory: 2048Mi
          limits:
            cpu: 2000m
            memory: 2048Mi
    sidecarInjector:
      enabled: true
    ingressGateways:
    - name: istio-ingressgateway
      enabled: true
      k8s:
        hpaSpec:
          maxReplicas: 5
          minReplicas: 1
          scaleTargetRef:
            apiVersion: apps/v1
            kind: Deployment
            name: istio-ingressgateway
          metrics:
            - type: Resource
              resource:
                name: cpu
                targetAverageUtilization: 60
        resources:
          requests:
            cpu: 100m
            memory: 128Mi
          limits:
            cpu: 1500m
            memory: 1024Mi
        strategy:
          rollingUpdate:
            maxSurge: "100%"
            maxUnavailable: "25%"
    egressGateways:
    - name: istio-egressgateway
      enabled: false
    citadel:
      enabled: true
            
  addonComponents:
    grafana:
      enabled: true
      k8s:
        replicaCount: 1
    kiali:
      enabled: true
      k8s:
        replicaCount: 1
    tracing:
      enabled: true

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: demo-virtual-service
  namespace: istio-system
spec:
  hosts:
  - "*"
  gateways:
  - istio-ingressgateway
  http:
  - match:
    - uri:
        prefix: /demo/
    route:
    - destination:
        port: 
          number: 8080
        host: demo-service.demo.svc.cluster.local

Содержание

1. transport: loopyWriter.run returning. connection error: desc = «transport is closing» #401
2. Comments
3. 1.19.2 kube-apiserver can’t write to etcd — «transport is closing» #95334
4. Comments
5. transport is closing error #2298
6. Comments
7. What version of gRPC are you using?
8. What version of Go are you using ( go version )?
9. What operating system (Linux, Windows, …) and version?
10. What did you do?
11. What did you expect to see?
12. grpc transport closing issues #1462
13. Comments
14. Client
15. Describe Your Environment
16. Expected Behavior
17. Actual Behavior
18. Footer
19. Go gRPC Noisy Transport Closing Log #2901
20. Comments
21. Footer

Description

Xingxing Xia

2021-02-02 11:09:53 UTC

Description of problem:
KAS/OAS/OauthAS logs spam: loopyWriter.run returning. connection error: desc = "transport is closing"
But seems these messages are not indicative of any problem we care about, so they quite confuse users

Version-Release number of selected component (if applicable):
4.7.0-0.nightly-2021-01-31-031653

How reproducible:
*Always*
The spam can be seen in any env on your hand, so will not attach must-gather

Steps to Reproduce:
1. $ oc logs --timestamps -n openshift-kube-apiserver -c kube-apiserver kube-apiserver-ip-10-143-1-199.ec2.internal > logs/kube-apiserver-ip-10-143-1-199.ec2.internal.log
$ oc logs --timestamps -n openshift-apiserver -c openshift-apiserver apiserver-6cc8bf5c8f-7gr7n > logs/apiserver-6cc8bf5c8f-7gr7n.log
$ oc logs --timestamps -n openshift-oauth-apiserver oauth-apiserver-6bd4fbd859-l2f8b > logs/oauth-apiserver-6bd4fbd859-l2f8b.log

2.
$ grep 'loopyWriter.run returning. connection error: desc = "transport is closing"' logs/kube-apiserver-ip-10-143-1-199.ec2.internal.log | wc -l
253
$ grep 'loopyWriter.run returning. connection error: desc = "transport is closing"' logs/apiserver-6cc8bf5c8f-7gr7n.log | wc -l
827
$ grep 'loopyWriter.run returning. connection error: desc = "transport is closing"' logs/oauth-apiserver-6bd4fbd859-l2f8b.log | wc -l
804

Take OAS for example:
$ grep 'loopyWriter.run returning. connection error: desc = "transport is closing"' logs/apiserver-6cc8bf5c8f-7gr7n.log | grep "^2021-02-02T09:50"
2021-02-02T09:50:02.522899544Z I0202 09:50:02.522863       1 controlbuf.go:508] transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2021-02-02T09:50:05.128339529Z I0202 09:50:05.128313       1 controlbuf.go:508] transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2021-02-02T09:50:13.314228703Z I0202 09:50:13.314204       1 controlbuf.go:508] transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2021-02-02T09:50:35.511715474Z I0202 09:50:35.511680       1 controlbuf.go:508] transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2021-02-02T09:50:45.454702141Z I0202 09:50:45.454672       1 controlbuf.go:508] transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2021-02-02T09:50:47.907317981Z I0202 09:50:47.907288       1 controlbuf.go:508] transport: loopyWriter.run returning. connection error: desc = "transport is closing"

Actual results:
2. KAS/OAS/OauthAS spam such logs, they confuse users

Expected results:
2. No such confusing spam

Additional info:
Bug 1844448#c0 once ever showed such logs too, now not see:
$ oc logs --timestamps -n openshift-etcd-operator etcd-operator-fb8cbf695-hlzf2 > logs/etcd-operator-fb8cbf695-hlzf2.log
$ grep 'loopyWriter.run.*connection error' logs/etcd-operator-fb8cbf695-hlzf2.log # none

Also not see in etcd container logs.

Comment 3

Michal Fojtik

2021-03-07 20:26:55 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 4

Fatima

2021-04-06 08:21:58 UTC

We have a customer facing this for kube-apiserver pods. One of the pods show:

~~~
$ grep 'loopyWriter.run returning. connection error: desc = "transport is closing"' kas1.logs | wc -l
13583
~~~

where kas1 is "oc logs <podname> -c kube-apiserver > kas1.logs" for one of the masters. This master is showing more than 60% cpu consumption and specifically this pod is consuming more cpu.

If any information is required please let me know I'll update the bug.

Comment 5

Fatima

2021-04-08 00:39:29 UTC

Dear team, 

Any updates here?

Thanks.

Comment 6

Fatima

2021-04-16 05:38:03 UTC

Dear team, 

Any updates here?

Thanks.

Comment 14

Sam Batschelet

2021-06-18 20:47:14 UTC

We will keep the BZ open until it lands.

Comment 18

Sandeep

2021-07-07 06:25:20 UTC

steps followed are :

1. Install cluster version : 4.9.0-0.nightly-2021-07-06-025559
2. check the logs of apiserver and saw the  message "loopyWriter.run returning. connection error: desc = "transport is closing"

The same issue is also seen in Server Version: 4.7.0-0.nightly-2021-07-06-050841

Comment 20

Sam Batschelet

2021-07-07 09:55:47 UTC

1.22 rebase has not landed in openshift so we can retest when that happens.

Comment 21

Mridul Markandey

2021-07-12 19:14:38 UTC

We have a customer facing the same issue that the kube-api server is consuming max of CPU resources and the Kube-apiserver pods logs shows this output:
~~~
ccResolverWrapper: sending update to cc: {[{https://localhost:2379  <nil> 0 <nil>}] <nil> <nil>}
2021-07-09T06:36:50.297990740Z I0709 06:36:50.297885      17 clientconn.go:948] ClientConn switching balancer to "pick_first"
2021-07-09T06:36:50.300944216Z I0709 06:36:50.298272      17 balancer_conn_wrappers.go:78] pickfirstBalancer: HandleSubConnStateChange: 0xc02705cd60, {CONNECTING <nil>}
2021-07-09T06:36:50.318796017Z I0709 06:36:50.313817      17 balancer_conn_wrappers.go:78] pickfirstBalancer: HandleSubConnStateChange: 0xc02705cd60, {READY <nil>}
2021-07-09T06:36:50.318796017Z I0709 06:36:50.315980      17 controlbuf.go:508] transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2021-07-09T06:36:52.532112913Z W0709 06:36:52.531817      17 admission.go:98] ClusterQuotaAdmission received non-meta object *unstructured.Unstructured
2021-07-09T06:36:52.582434039Z W0709 06:36:52.582254      17 admission.go:98] ClusterQuotaAdmission received non-meta object *unstructured.Unstructured
2021-07-09T06:36:52.731282776Z W0709 06:36:52.731187      17 admission.go:98] ClusterQuotaAdmission received non-meta object *unstructured.Unstructured
2021-07-09T06:36:52.931948178Z W0709 06:36:52.931846      17 admission.go:98] ClusterQuotaAdmission received non-meta object *unstructured.Unstructured
2021-07-09T06:36:53.131199569Z W0709 06:36:53.131091      17 admission.go:98] ClusterQuotaAdmission received non-meta object *unstructured.Unstructured
2021-07-09T06:36:53.330927116Z W0709 06:36:53.330835      17 admission.go:98] ClusterQuotaAdmission received non-meta object *unstructured.Unstructured
2021-07-09T06:36:53.531801993Z W0709 06:36:53.531689      17 admission.go:98] ClusterQuotaAdmission received non-meta object *unstructured.Unstructured
~~~
Can you suggest a workaround for this? If more information is required please let me know I'll update the bug.

Comment 22

Mridul Markandey

2021-07-14 13:35:00 UTC

Hello Team, 

Any update on this? 

Thanks

Comment 23

Sam Batschelet

2021-07-14 13:47:10 UTC

There is no workaround for etcd client balancer gRPC logs in apiserver, we are going to improve this in 4.9.

>2021-07-09T06:36:50.297990740Z I0709 06:36:50.297885      17 clientconn.go:948] ClientConn switching balancer to "pick_first"
>2021-07-09T06:36:50.300944216Z I0709 06:36:50.298272      17 balancer_conn_wrappers.go:78] pickfirstBalancer: HandleSubConnStateChange: 0xc02705cd60, {CONNECTING <nil>}
>2021-07-09T06:36:50.318796017Z I0709 06:36:50.313817      17 balancer_conn_wrappers.go:78] pickfirstBalancer: HandleSubConnStateChange: 0xc02705cd60, {READY <nil>}
>2021-07-09T06:36:50.318796017Z I0709 06:36:50.315980      17 controlbuf.go:508] transport: loopyWriter.run returning. connection error: desc = "transport is closing"

This is not root cause for CPU if you have issues around that you should start a new bug against apiserver.

Пожалуйста, ответьте на эти вопросы, прежде чем отправлять свою проблему.

Какую версию gRPC вы используете?

1.18.0

Какую версию Go вы используете ( go version )?

1.11.5

Какая операционная система (Linux, Windows,…) и версия?

Alpine Linux 3.9 на движке Google Kubernetes Engine

Что ты сделал?

После обновления я заметил значительное увеличение количества ошибок grpc, приводящих к неудачным запросам и сбоям в обслуживании.

Мы не используем никаких настроек подключения на клиентах, и у нас нет никаких специальных настроек на сервере (keepalive, fastfail и т. Д.). Единственное, что у нас есть на соединениях, это Mutual TLS. Примерно это настроено так:

Клиент:

creds := grpc.WithTransportCredentials(credentials.NewTLS(&tls.Config{
        RootCAs:      certPool,
        Certificates: []tls.Certificate{cert},
        MinVersion:   tls.VersionTLS12,
}))
grpc.Dial("foo.foo.svc.cluster.local:80", creds)

Сервер:

creds := grpc.Creds(credentials.NewTLS(&tls.Config{
    Certificates:             []tls.Certificate{cert},
    ClientCAs:                certPool,
    ClientAuth:               tls.RequireAndVerifyClientCert,
    MinVersion:               tls.VersionTLS12,
    NextProtos:               []string{"h2"},
    PreferServerCipherSuites: true,
    CurvePreferences: []tls.CurveID{
        tls.CurveP256,
        tls.X25519,
    },
    CipherSuites: []uint16{
        tls.TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
        tls.TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
        tls.TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
        tls.TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
        tls.TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
        tls.TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
    },
}))
grpc.NewServer(creds)

Это может быть связано с одной из этих двух других проблем.
https://github.com/grpc/grpc-go/issues/2653
https://github.com/grpc/grpc-go/issues/2636

Основываясь на отзывах по одной из связанных выше проблем, я установил эти переменные ENV для одной службы, у которой было много сбоев: GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info

Я добавил (__GRPC CALL HERE__) в конец строк журнала ниже, где ошибка была зарегистрирована как неудачный вызов grpc, который мы сделали.

WARNING: 2019/03/01 04:41:42 grpc: addrConn.createTransport failed to connect to {foo.foo.svc.cluster.local:80 0  <nil>}. Err :connection error: desc = "transport: authentication handshake failed: context deadline exceeded". Reconnecting...
INFO: 2019/03/01 04:41:42 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 04:41:42 pickfirstBalancer: HandleSubConnStateChange: 0xc000806290, TRANSIENT_FAILURE
timestamp=2019-03-01T04:41:42.887562062Z level=error error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: authentication handshake failed: context deadline exceeded"" (__GRPC CALL HERE))
INFO: 2019/03/01 04:41:43 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 04:41:43 pickfirstBalancer: HandleSubConnStateChange: 0xc000806290, CONNECTING
INFO: 2019/03/01 04:41:44 Subchannel Connectivity change to READY
INFO: 2019/03/01 04:41:44 pickfirstBalancer: HandleSubConnStateChange: 0xc000806290, READY
INFO: 2019/03/01 04:45:22 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/03/01 04:45:22 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 04:45:22 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/03/01 04:45:22 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 04:45:23 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 04:45:23 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 04:45:28 Subchannel Connectivity change to READY
INFO: 2019/03/01 04:45:28 Subchannel Connectivity change to READY

INFO: 2019/03/01 05:34:23 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 05:34:23 Subchannel Connectivity change to READY
INFO: 2019/03/01 05:35:25 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/03/01 05:35:25 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 05:35:27 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 05:35:32 Subchannel Connectivity change to READY
INFO: 2019/03/01 05:35:59 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 05:35:59 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/03/01 05:36:01 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 05:36:01 Subchannel Connectivity change to READY
INFO: 2019/03/01 05:38:19 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 05:38:19 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/03/01 05:38:19 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 05:38:19 pickfirstBalancer: HandleSubConnStateChange: 0xc0008293d0, TRANSIENT_FAILURE
INFO: 2019/03/01 05:38:19 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
timestamp=2019-03-01T05:38:19.972966567Z level=error error="rpc error: code = Unavailable desc = transport is closing" (__GRPC CALL HERE__)
INFO: 2019/03/01 05:38:19 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/03/01 05:38:19 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 05:38:19 pickfirstBalancer: HandleSubConnStateChange: 0xc000806290, TRANSIENT_FAILURE
INFO: 2019/03/01 05:38:21 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 05:38:21 pickfirstBalancer: HandleSubConnStateChange: 0xc0008293d0, CONNECTING
INFO: 2019/03/01 05:38:21 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 05:38:21 pickfirstBalancer: HandleSubConnStateChange: 0xc000806290, CONNECTING
INFO: 2019/03/01 05:38:21 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 05:38:21 Subchannel Connectivity change to READY
INFO: 2019/03/01 05:38:21 transport: loopyWriter.run returning. connection error: desc = "transport is closing"

INFO: 2019/03/01 16:13:05 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 16:13:05 pickfirstBalancer: HandleSubConnStateChange: 0xc0008293d0, TRANSIENT_FAILURE
INFO: 2019/03/01 16:13:05 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
timestamp=2019-03-01T16:13:05.92908361Z level=error error="rpc error: code = Unavailable desc = transport is closing" (__GRPC CALL HERE__)
INFO: 2019/03/01 16:13:07 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 16:13:07 pickfirstBalancer: HandleSubConnStateChange: 0xc0008293d0, CONNECTING
INFO: 2019/03/01 16:13:07 Subchannel Connectivity change to READY
INFO: 2019/03/01 16:13:07 pickfirstBalancer: HandleSubConnStateChange: 0xc0008293d0, READY
INFO: 2019/03/01 16:20:17 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 16:20:17 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/03/01 16:20:18 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 16:20:23 Subchannel Connectivity change to READY
INFO: 2019/03/01 16:42:24 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 16:42:24 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/03/01 16:42:25 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 16:42:25 Subchannel Connectivity change to READY
INFO: 2019/03/01 17:20:47 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/03/01 17:20:47 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 17:20:49 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 17:20:54 Subchannel Connectivity change to READY
INFO: 2019/03/01 17:43:01 Subchannel Connectivity change to TRANSIENT_FAILURE
INFO: 2019/03/01 17:43:01 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/03/01 17:43:02 Subchannel Connectivity change to CONNECTING
INFO: 2019/03/01 17:43:07 Subchannel Connectivity change to READY

Была ли эта страница полезной?

0 / 5 — 0 рейтинги

[{
	"name": "listener_0",
	"address": {
		"socket_address": {
			"address": "0.0.0.0",
			"port_value": 8080
		}
	},
	"filter_chains": [{
		"filters": [{
			"name": "envoy.http_connection_manager",
			"config": {
				"codec_type": "auto",
				"stat_prefix": "ingress_http",
				"route_config": {
					"name": "local_route",
					"virtual_hosts": [{
						"name": "local_service",
						"domains": [
							"*"
						],
						"routes": [{
							"match": {
								"prefix": "/App.Grpc.MyApp1"
							},
							"route": {
								"cluster": "main_service",
								"max_grpc_timeout": "0s"
							}
						}],
            "cors": {
              "allow_origin": [
                "*"
              ],
              "allow_methods": "GET, PUT, DELETE, POST, OPTIONS",
              "allow_headers": "keep-alive, user-agent, cache-control, content-type, content-transfer-encoding, Authorization, x-ip, x-accept-content-transfer-encoding, x-accept-response-streaming, x-user-agent, x-grpc-web, grpc-timeout",
              "max_age": "1728000",
              "expose_headers": "grpc-status, grpc-message",
              "enable": true
            }
					}]
				},
				"http_filters": [{
						"name": "envoy.cors"
					},
					{
						"name": "envoy.grpc_web"
					},
					{
						"name": "envoy.router"
					}
				]
			}
		}]
	}]
}]

[{
	"name": "MyApp1",
	"connect_timeout": "0.25s",
	"type": "logical_dns",
	"lb_policy": "round_robin",
	"http2_protocol_options": {},
	"hosts": [{
		"socket_address": {
			"address": "host.docker.internal", # also tried docker service name my_app
			"port_value": 50053
		}
	}]
}]