@jthiltges commented on this pull request.
In src/XrdTls/XrdTlsSocket.cc:
> @@ -352,6 +353,14 @@ int XrdTlsSocket::Diagnose(const char *what, int sslrc, int tcode) "TLS error rc=%d ec=%d (%s) errno=%d.", sslrc, eCode, XrdTls::ssl2Text(eCode), eNO); XrdTls::Emsg(pImpl->traceID, eBuff, true); + // Report any additional queued errors + char eBuffSSL[120]; int eQueue; + while ((eQueue = ERR_get_error())) { + ERR_error_string_n(eQueue, eBuffSSL, sizeof(eBuffSSL)); + snprintf(eBuff, sizeof(eBuff), + "TLS error queue: ec=%d, %s", eQueue, eBuffSSL); + XrdTls::Emsg(pImpl->traceID, eBuff, true); + }
Great, I didn't realize Emsg handled that. I had set xrd.trace all
, but hadn't noticed log or stderr entries for the error queue entries.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1