Weird that error message should have errno attached:
SSL_CLR_ERR_INCR_DYN_STAT(ssl_error_ssl,
"SSLNetVConnection::sslClientHandShakeEvent,
SSL_ERROR_SSL errno=%d", errno);
Your version must be older, can you hack together a debug build that logs
errno?
Brian
On Fri, Nov 14, 2014 at 4:15 PM, James Peach <jpe...@apache.org> wrote:
>
> > On Aug 6, 2014, at 10:20 AM, James Peach <jpe...@apache.org> wrote:
> >
> > On Aug 5, 2014, at 12:16 PM, Brian Geffon <briangef...@gmail.com> wrote:
> >
> >> Technically you'd probably aggregate all of these into a single variable
> >> for production monitoring, but having insight into the individual
> failure
> >> scenarios could prove to be very valuable.
> >
> > I'm still very dubious about these stats.
> >
> > SSL_ERROR_WANT_WRITE, SSL_ERROR_WANT_READ, and
> SSL_ERROR_WANT_X509_LOOKUP boil down to rescheduling the I/O. Hard to see
> how a metric for that is useful. The other things here end up as an error
> or EOF. Again, hard to see how this is helpful as a metric.
> >
> > Handshake errors (client and server) seems like they could be
> interesting to monitor, but these are bundled in "ssl_error_ssl", so you'll
> really have no idea what is happening.
>
> Well, I now have a handshake error in production and no logging :-/ Does
> anyone know how I can debug this?
>
> The only thing I can get out of logs now is this:
>
> [Nov 14 23:58:13.204] Server {0x2aaaba64a700} DEBUG:
> <SSLNetVConnection.cc:735 (sslClientHandShakeEvent)> (ssl.error)
> SSLNetVConnection::sslClientHandShakeEvent, SSL_ERROR_SSL
>
> J
