Me again...
Now we're getting this in the log files:
@400000003b44845219ec0e14 status: local 0/10 remote 3/20 exitasap
@400000003b44845219ec73a4 delivery 760867: deferral: qmail-remote_crashed./
@400000003b44845219ece8d4 status: local 0/10 remote 2/20 exitasap
@400000003b44845219ed524c delivery 760873: deferral: qmail-remote_crashed./
@400000003b44845219edc77c status: local 0/10 remote 1/20 exitasap
@400000003b44845219ee2d0c delivery 760883: deferral: qmail-remote_crashed./
@400000003b44845219eea23c status: local 0/10 remote 0/20 exitasap
Here's what we've always used for the startup of qmail, and never had a problem (till
now):
/bin/csh -cf '/var/qmail/rc &'
tcpserver -R -c 150 0 110 /var/qmail/bin/qmail-popup mail.mydomain.net
/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir &
tcpserver -p -x /etc/tcp.smtp.cdb -c 150 0 smtp /var/qmail/bin/qmail-smtpd &
The server seems to be sending and receiving mail fine though. The only thing I'm
noticing is that the size of the unprocessed queue messages is growing.
Any ideas?
Thanks again
David
> On Thu, Jul 05, 2001 at 11:05:40AM -0400, David Gartner allegedly wrote:
> > Hey all,
> >
> > I have a slight problem. I got some calls that the mail server was taking 5
> > hours to send email, so I checked out the mail server. I had 3 connections to
> > some mail server (all the same) and all the other qmail-remotes were enclosed in
> > brackets [qmail-remote]. Not knowing what this was, I did a 'killall
> > -HUP qmail-remote'. The 'unclogged' the remote process and it started
> > delivering the messages that were on hold. Can anyone tell me what might have
> > cause this
