Michael Nguyen writes:
Ok... so now the other question. Would you agree that we're hitting this timeout? This is what we get flooded with when it happens: pop3d: authdaemon: s_connect() failed: Resource temporarily unavailable pop3d: authentication error: Resource temporarily unavailable
Yes.
What's odd is, none of our other applications complain like this. We have a number of applications that make database calls and they don't do this. Some are written in C (like our friend Courier) and some are in Java.
They use larger timeouts.
When these errors come, they come in bunches and typically I'm able to go to that server and still authenticate so it's not failing all of the connections, just a fraction of them. My take is that Authdaemond is just being touchier than our other apps and that adjusting this timeout could help. Would you agree, Sam?
Yes. This is an early indication that you need to throw more resources. 15 seconds, or so, should be more than enough to process a single authentication request.
pgp9sXsC4Ss96.pgp
Description: PGP signature
