Forum Discussion
hui_37443
Nimbostratus
Nimbostratusauth_result fired twice?
We have implemented an iRule to do OCSP check, based on the prize winner http://devcentral.f5.com/Default.aspx?tabid=108. When it encounters an error, it doesn't resume the suspended SSL::handshake. ...
hui_37443Nimbostratus
NimbostratusAaron,
It happened on production and almost impossible for me to play around. Anyway, the issue has since been resolved. It has turned out the root cause is DNS server down. The OCSP server URL can not be resolved. However, there is potentially something wrong with the exception handling inside F5 process.
My assumption is that when the DNS resolution fails an exception is thrown so the OCSP authentication fails straight away. However, there is the normal process thread not be cleaned up and still in block waiting status, and finally gets timed out. Hence the "two-time fired" authe_result event.
Craig,
I am not a network expert, but I guess the LnkSys router should be doing some trick that confuses F5 session management...
Regards,
