Re: [squid-users] Error negotiating SSL connection on FD 33: WSAEWOULDBLOCK, Resource temporarily unavailable. (10035)

On 19/09/2012 2:07 a.m., McGoldrick Pat wrote:
> I'm using squid 2.7.
>
> I have set squid up to be in front of websphere. I'm getting the error every 5 seconds. We only get it when websphere is running, so it would seem it's between websphere and squid.
>
> C:\squid\var\logs
>
> Cache.log
> This happens every 5 seconds.
>
> 2012/09/18 12:04:30| clientNegotiateSSL: Error negotiating SSL connection on FD 33: WSAEWOULDBLOCK, Resource temporarily unavailable. (10035)
>
>
> In C:\squid\etc\squid.conf I have tried configuring the connection to the back end two ways,
>
> Verifying the cert
> cache_peer machine1.ii.net parent 9443 0 no-query originserver login=PASS name=ibm_was ssl sslflags=NO_DEFAULT_CA sslcafile=C:/squid/var/truststore/ machine1.pem ssldomain= machine1.ii.net
>
> Not verifing the cert
> cache_peer machine1.ii.net parent 9443 0 no-query originserver login=PASS name=ibm_was ssl sslflags=DONT_VERIFY_PEER
>
>
> Both ways give the same error
>
> Any ideas?

The message is produced by https_port when receiving a supposedly HTTPS
connection.

According to OpenSSL documentation:
"The TLS/SSL handshake was not successful because a fatal error occurred
either at the protocol level or a connection failure occurred. The
shutdown was not clean. It can also occur of action is need to continue
the operation for non-blocking BIOs. Call |SSL_get_error()| with the
return value *ret* to find out the reason. "

ssl_get_error() is what is producing that "Resource temporarily
unavailable. (10035)" part.

Amos
Received on Wed Sep 19 2012 - 01:10:30 MDT