One more time,
I did tcpdump and strace on stuck qmail-remote for over an hour.
strace shows that qmail-remote is stuck on: 'read(3', and tcpdump shows
that nothing comes in.
On Fri, Jun 08, 2001 at 03:13:54PM +0000, Mark wrote:
> > processed those 1500 messages in less than 30 minutes. However, it left
> > behind another handfull of stuck qmail-remote processes. Other messages
> > were undeliverable and left in the queue, and still others were sent back to
> > sender with permanent errors.
>
> What do you mean by "stuck"? Do you mean they *never* go away - even
> after a day or two? As others have pointed out, a slow delivery can
> take a long, long time. That's not necessarily a problem, that's just
> the way it is.
>
> To find out a bit more about what a "stuck" qmail-remote is doing, you
> may want to ktrace it and show us the output. Find the process id of the
> stuck qmail-remote and then as root go: ktrace -p thepid
>
> Leave that running for at least an hour and show us the output. Yes, I
> mean at least an hour.
>
>
> Regards.
>
--
Eugene Miretskiy <[EMAIL PROTECTED]>
InVision.com, INC. (631) 543-1000
www.invision.net / www.longisland.com
