Hi Eric, Thanks for your reply. Unfortunately I cannot post the code I'm running. I'm using subprocess.call but it's the same thing basically (changed it to Popen just in case and I still got the error). I tried setting GRPC_ENABLE_FORK_SUPPORT to 0 in the Server and Clients environments, but that didn't make a difference.
If I remove the subprocess.call/Popen, I don't get the exception. I've been trying different combinations and I've found that the channel created in the C++ client doesn't have anything to do with the exception. If I open a C++ subprocess that does nothing (just returning 0 from its main method), I do get the exception. So, it seems that just creating the subprocess from the Python client is causing that exception to be thrown. I will try to reproduce the error with code that I can share tomorrow. Just wanted to give you an update before finishing today in case that could shed any light on what could be happening. Thanks, Alex. On Wednesday, February 20, 2019 at 7:04:51 PM UTC, Eric Gribkoff wrote: > > Can you post the code you're using to reproduce this error? If you're > using subprocess.Popen (or otherwise using fork+exec) to start the C++ grpc > client process, the C++ client itself cannot be interfering with the Python > process. Something could be going wrong in the gRPC core fork handlers, > however - you can try running with the environment variable > `GRPC_ENABLE_FORK_SUPPORT=0` to disable this feature and see if it fixes > the issue. > > Also, in your step 5 you note that the C++ client isn't communicating with > the server. If you remove the fork+exec of a C++ subprocess altogether, do > you still see this intermittent exception in the Python client? > > Eric > > On Wed, Feb 20, 2019 at 6:57 AM Alex <[email protected] <javascript:>> > wrote: > >> I should add that the Python client application which owns the Python >> grpc client is the one that runs the C++ grpc client as a subprocess in >> case that makes a difference. >> >> -- >> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/grpc-io. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/grpc-io/b323fac3-978b-47c1-b1fa-555c2f62b544%40googlegroups.com >> >> <https://groups.google.com/d/msgid/grpc-io/b323fac3-978b-47c1-b1fa-555c2f62b544%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/0960b49d-7e8c-4fb3-b17e-f424feedc65b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
