-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failed to receive the preface from client -- triggered by tcp health check #875
Comments
we are working on improving grpc logging (this should only appear in debugging mode). |
I had the same issue.
Is there any work-in-progress branch as public? |
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>
.
|
Thanks. |
hi , do you have any solutions for this problem ? for i have met the same error. |
Log spamming will be alleviated with grpclog changes. We have #922 for the API change. |
@menghanl i have resolved my problem . The reason is that i set the wrong server-hostname when running tls |
@imoverclocked |
@xuss Can you throw some more light on what exactly are you seeing?
|
I'm running a gRPC server in an environment that checks health via tcp open or tcp half-open. This triggers:
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.
The text was updated successfully, but these errors were encountered: