Hi, gRPC provides environmental variables that enables trace log.
The simplest pair will be "GRPC_VERBOSITY=debug" and "GRPC_TRACE=all". For more finer granularity, please check https://github.com/grpc/grpc/blob/master/doc/environment_variables.md. Lidi Zheng On Wednesday, June 12, 2019 at 7:00:16 AM UTC-7, zheco...@gmail.com wrote: > > Hi all, > > My gRPC client raised this error > > ... > File "/home/work/code/venv/site-packages/grpc/_channel.py", line 466, in > _end_unary_response_blocking > raise _Rendezvous(state, None, None, deadline) > _Rendezvous: <_Rendezvous of RPC that terminated with: > status = StatusCode.UNAVAILABLE > details = "OS Error" > debug_error_string= > "{"created":"@1560255578.803770511","description":"Error received from > peer","file":"src/core/lib/surface/call.cc","file_line":1036,"grpc_message":"OS > > Error","grpc_status":14}" > > It says "Error received from peer", so my server send this status. And it > also says "OS Error". > > How can inspect what is going on in my server when it says "OS Error"? I > expected some startup options or environment variables. > > Thanks. > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/938c4e5b-8ef7-419f-9255-c73679d20837%40googlegroups.com.
