Not really. gRPC logs are enabled through an env var, and even then, you
need to enable specific components.
Anyway, I found the fix was I needed to call
tlsOpts.watch_root_certs();
tlsOpts.watch_identity_key_cert_pairs();
If these need to be called, I don't see why I should have to call them
Are there any logs leading up to this? If the the SIGABRT is coming from
gRPC, I'd expect to see a log of the source code line that triggered the
abort.
If the issue is still not obvious, a runnable repro might help.
On Thursday, February 1, 2024 at 5:23:45 PM UTC-8 Tim wrote:
> Hi, I'm gettin
