On 8/8/12 1:50 PM, Mark Montague wrote:
> Has anyone seen a problem with CosignModule for IIS where users
> sometimes, but not always, receive a 503 "Service unavailable" message
> when they first try to access a cosign-protected resource?

Yeah. The fix

    94a646c251ec237006a61e0aecdc0dd8c8f8d43c
    Fix for hanging socket connections.


handles one case we had, but apparently not yours.

> - So far, we have only observed the failure on the initial URL
> validation.  If the user re-loads the page, the validation succeeds and
> the user is able to use the web application normally without problem.
>
> - ConnectionList::CheckCookie is using a pool of already-open
> connections but is experiencing read errors.  The first read error
> ("data(4)", above) is on a connection on which TLS has already been
> started -- CosignModule sends a CHECK command, and then is unable to
> read the response.  It then tries four other connections, none of which
> have had TLS started, sends the STARTTLS command, and then is unable to
> read the responses.

The problem we saw (and that patch fixed) and yours I think are related: 
the initial connections happened a while ago (not in the log you sent), 
and the cosignd idle timer (default 4 minutes) activated on the other 
five connections and closed them. In the case you presented, the filter 
was able to use the first connection without needing to check the others 
(perhaps more than once), so it was still active, but 533 return caused 
the filter to need to check the other connections. However, they had all 
been idle-closed by then.

The re-load works because the filter re-initializes all 6 connections 
and uses them immediately, so they're still connected.

In our case, all four of the website filter's connections (that's our 
total) were idle-dropped before they could be used.

-Phil

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

Reply via email to