Hello!
This is def. not the problem. Cause i've tested it myself and i've not
closed the connection. Also the server receives my commands but i do not
receive any output. If this happens the first time. The child never
works correctly again until it is killed.
So i see in the log:
[25973]: Could not print [220 XXX ESMTP qpsmtpd 0.40 ready; send us your
mail, but not your spam.]: No such file or directory
But if i send an a you see the following:
[25973]: Unrecognized command 'a'
But in the telnet session i didn't get any output. Cause:
Could not print [500 Unrecognized command]: Bad file descriptor
So the first time i get always a "No such file or dir..." second time
and any other time "Bad file descriptor"
I can reproduce this on all tested machine (about 50). All with Debian
3.1 or Debian 4.0 - Perl 5.8.4 or 5.8.8.
Stefan
Peter J. Holzer schrieb:
On 2007-07-02 13:05:03 +0200, Stefan Priebe wrote:
Stefan Priebe schrieb:
2.) The real Problem is, that it hangs after running about 1 hour or
so. I'm using about 60 childs with about 20 new connections per second.
After a while more and more childs hangs in $d->accept(). And you did
not get any answer from the SMTP anymore. Any idea to that?
I've found out some more information. They seem to hang at another point
as i aspected.
In the debug log i see the following message:
Could not print [220 XXX ESMTP qpsmtpd 0.40 ready; send us your mail,
but not your spam.]: No such file or directory
Looks like the client closed the connection before the server sent the
greeting (although I'd have expected a slightly different error message
("Bad file descriptor" or "Connection reset by peer") in this case).
That happens, especially if you use check_earlytalker.
I think the server process should just close the current connection and
accept the next one in this case (Simply exiting and letting the parent
restart the process would work, too, but defeats the purpose of running
prefork).
hp
