On Jul 13, 2005, at 3:50 PM, Michael Nguyen wrote:
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
Sam can tell me if I'm off base here, but I don't think you're
hitting the timeout. I think what's happening is that all of your
authdaemon processes are getting stuck doing queries and can't accept
new connections. New connection attempts will fill up the socket
queues, and once those are full you'll start seeing that error in
your logs. If your authdaemon were timing out connections, you'd
probably see log messages from the authdeamon process rather than pop3d.
My question is, what kind of "major changes" are you making that
cause the SQL server to hang?
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.
I don't think so. In fact, I think that if you increase the timeout,
you'll actually see more errors. When the SQL server hangs, your
authdaemon processes will just be backed up for longer periods.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
