httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wilda, Jet" <>
Subject RE: [users@httpd] How to get SSL handshake errors logged
Date Thu, 14 Aug 2008 17:51:40 GMT

	Here is what I saw:

[Wed Aug 13 09:54:24 2008] [info] [client] SSL library error 1 in handshake
[Wed Aug 13 09:54:24 2008] [info] SSL Library Error: 336027900 error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown
protocol speaking not SSL to HTTPS port!?
[Wed Aug 13 09:54:24 2008] [info] [client] Connection closed to child 0 with
abortive shutdown (server


-----Original Message-----
From: William A. Rowe, Jr. [] 
Sent: Thursday, August 14, 2008 1:43 PM
Subject: Re: [users@httpd] How to get SSL handshake errors logged

Wilda, Jet wrote:
> Hi,
> 	How do I get Apache httpd (2.0.X and 2.2.X) to log SSL handshake errors?  I found that
if I set ‘LogLevel info’ they will be logged to the error log.  However it then logs way
to much stuff.  What I need is a way to just log all the SSL errors especially the handshake
errors.  Thanks for any and all help ☺

I thought that the failure itself was logged at level 'error'.  Certainly,
at level 'warning'.  If this is not so, we should review the error levels
of the various emits from mod_ssl.

Feel free to sniff the LogLevel info for one failed connection, and point
out the one error that you believe should have been logged at warn/error.

Notice that you can tell which are which right in the logs, just look for
[info], [warn] etc on each log line.

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:
Learn more about Chase Paymentech Solutions,LLC payment processing services at

THIS MESSAGE IS CONFIDENTIAL.  This e-mail message and any attachments are proprietary and
confidential information intended only for the use of the recipient(s) named above.  If you
are not the intended recipient, you may not print, distribute, or copy this message or any
attachments.  If you have received this communication in error, please notify the sender by
return e-mail and delete this message and any attachments from your computer.

View raw message