Josiah Hobson <[EMAIL PROTECTED]> wrote:
> Now the smtp socket seems to die or hang or something after 12-24 hours.
> netstat shows it as still listening, but a telnet to port 25 will connect
> but not initiate a session or respond to any commands. Applications
> attempting to send mail will of course timeout waiting for a response.
If tcpserver hits the concurrency limit you've specified (default 40),
additional connections will go into this limbo state until one of the existing
connections exits. Perhaps something is tying up connections? Make sure you
use the -v option of tcpserver, and capture/log tcpserver's output. That will
log status lines, showing you what the concurrency is at every connection. If
it goes steadily up, this is your problem.
> Restarting qmail with `qmail restart` does NOT solve the problem, nor does
> restarting the OS.
Restarting the OS? You mean rebooting? That clears the TCP connection
backlog in every OS I know :).
> Simply rebuilding the cdb with `qmail cdb` DOES HOWEVER fix the problem
> immediately. So it does seem that the tcp.smtp.cbd file is being corrupted.
It appears so. Are you logging tcpserver's output and using the -v flag?
> I don't see anything anywhere in the logs to indicate that something bad
> is happenening. I am no qmail expert so I'm about at the end of my
> troubleshooting capability. Anybody who can shed some light on the inner
> workings of this cdb so I can figure out why it is being corrupted?
"tcprules" can't leave a corrupt .cdb file -- it writes to a temp file, and
only moves it into place of the original if successful.
> I mean, I could always cron a `qmail cdb` script and probably avoid the
> issue, but I hate not get down to the root cause.
I would guess filesystem or memory corruption.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
