On Fri, 11 Apr 2008, Charlie Brady wrote: > > Second (major), when the limit is exceeded, qpsmtpd hangs. A few hours > > ago, my logs show that I was at 29/30 and 30/30 quite steady, and then > > everything suddently stopped. For whatever reason, forkserver would > > not complete or let go of the 31 connections it already had, and would > > not accept any more. I had to restart the service to recover. > > I suspect that the only reason you hit the limit was because some plugin > was not returning. I suspect that qpsmtpd wasn't actually hanging, it > just wasn't accepting more connections.
Tracing a non-returning plugin could be very difficult :-( Seems strange that all those connections might hang at the same point. If it happens again, I suppose I could trace PIDs in the process table. > qpsmtpd has a long-standing problem that timeouts are not applied to > plugins, only to core qpsmtpd code. Sounds like that would be a better solution, though. Might anyone be working on it? Thank-you.
