failed to receive the preface from client -- triggered by tcp health check

[imoverclocked]

I'm running a gRPC server in an environment that checks health via tcp open or tcp half-open. This triggers:

2016/09/02 17:58:25 transport: http2Server.HandleStreams failed to receive the preface from client: read tcp 1.1.1.1:31703->2.2.2.2:54388: read: connection reset by peer

which fills up logs over time. Any chance of squelching the message, even with an option?

https://github.com/grpc/grpc-go/blob/master/transport/http2_server.go#L231

Cheers.

[iamqizhao]

we are working on improving grpc logging (this should only appear in debugging mode).

[enm10k]

I had the same issue.
And I want this to be fixed for our production use.

we are working on improving grpc logging (this should only appear in debugging mode).

Is there any work-in-progress branch as public?
If no one is working on this now, I'll do.

[MakMukhi]

Hey, We are working on this; There's a PR out. However, the engineer working on it is ooo and we'll be able to give a status once he's back. Best, Mak

…

On Tue, Jan 17, 2017 at 9:16 AM, enm10k ***@***.***> wrote: I had the same issue. And I want this to be fixed for our production use. we are working on improving grpc logging (this should only appear in debugging mode). Is there any work-in-progress branch as public? If no one is working on this now, I'll do. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#875 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATtnR5iRDt5jARYYvooF2Hnk554GphSbks5rTPdWgaJpZM4Jz8oI> .

[enm10k]

Thanks.
I'm waiting for his back.

[hsaliak]

@MakMukhi @menghanl can you reference the PR here and close the issue if it's already resolved?

[CocoaWang]

hi , do you have any solutions for this problem ? for i have met the same error.

[menghanl]

Log spamming will be alleviated with grpclog changes.

We have #922 for the API change.
I also have the change to use different log levels in gRPC ready, will send that out when the API change is merged.

[CocoaWang]

@menghanl i have resolved my problem . The reason is that i set the wrong server-hostname when running tls

[dyxushuai]

@imoverclocked
This error is still existing for me with version v1.7.0
Do you have any solutions for this problem?

[MakMukhi]

@xuss Can you throw some more light on what exactly are you seeing?

1. Is your log spammed by errors originating in transport? Perhaps, consider setting your log verbosity level to 1. grpclog

2. Are you unable to connect because of a specific transport error? Please share more information, possible a reproduction.