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 getting a SIGABRT when starting a gRPC service using TLS. > > std::shared_ptr<grpc::experimental::FileWatcherCertificateProvider> > cert_provider(new > grpc::experimental::FileWatcherCertificateProvider(server_key_path, > server_cert_path, ca_cert_path, 10)); > grpc::experimental::TlsServerCredentialsOptions tlsOpts(cert_provider); > tlsOpts.set_cert_request_type > (grpc_ssl_client_certificate_request_type::GRPC_SSL_REQUEST_AND_REQUIRE_CLIENT_CERTIFICATE_AND_VERIFY); > > std::shared_ptr<grpc::ServerCredentials> tlsCreds = grpc::experimental:: > TlsServerCredentials(tlsOpts); > builder.AddListeningPort(uri, tlsCreds); > builder.BuildAndStart(); > > Is there some other precondition I'm missing? > -- 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/799d53de-15b5-4fd2-964e-714a885e9747n%40googlegroups.com.
