I had the same problem, after I did this correction, no more error
messages !
You have my vote to add this trick to the recommendations !
Peter.
"[EMAIL PROTECTED]" wrote:
>
> > I'd bet that this is idle server maintenance (taking down a child
> > process which isn't necessary). The non-SSL p
> I'd bet that this is idle server maintenance (taking down a child
> process which isn't necessary). The non-SSL path doesn't log an error
> for a dummy connect but evidently the SSL path does.
>
> The connect to itself isn't a bug, though it would be nice to avoid the
> SSL complaints. Try sw
You may want to try actually grabbing a couple-byte monitor page in your case from the
load balancers and parse it and look for a special string inside it, that's what we do
and that works well. This method not only tests if a connection is being opened, but
more thoroughly tests server intern
On Thu, Aug 29, 2002 at 09:21:27PM -0400, Jeff Trawick wrote:
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>
> > Looking into the matter, I discovered that this error is logged whenever a
> > connection from localhost to localhost:443 is made. The errors ALWAYS occur > >
>after apachectl s
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Looking into the matter, I discovered that this error is logged whenever a
> connection from localhost to localhost:443 is made. The errors ALWAYS occur
> after apachectl startssl; they never occur with apachectl start.
I'd bet that this is idl
I apologize if this (bug?) has already been brought up or resolved earlier.
I noticed a frequently occuring error being logged:
[error] Spurious SSL handshake interrupt [Hint: Usually just one of those
OpenSSL confusions!?]
Looking into the matter, I discovered that this error is logged whenev
