"Matt Hubbard" <[EMAIL PROTECTED]> wrote:
>Fairly frequently throughout an average day, my preprocessed queue will
>begin to grow steadily and not get processed. In most cases, if this is
>ignored, it resumes processing eventually. Sometimes after 15 or so minutes,
>sometimes after a couple of hours, but at bad times, it can fail to clear
>out the preprocessed queue for days. I've checked the logs, and in no case
>is the concurrency peaked during this problem(in fact, local is usually low
>at 1/120 and remote usually at about 20 to 40/120), though I'm not sure if
>that would be related, anyway.
Strange.
>The first thing I checked, of course, is the /var/qmail/queue/lock/trigger
>file, as noted in the archives. As far as I can tell, it looks correct.
That would ahve been my first suggestion.
>Here is an example of my problem at 11:14am:
>
>qmail-qstat output:
>messages in queue: 228
>messages in queue but not yet preprocessed: 63
>
>trigger file at the time:
>prw--w--w- 1 qmails qmail 63 Aug 6 11:14 trigger
Notice 63 unpreprocessed messages and 63 bytes in trigger? Not a
coinicidence. qmail-send isn't reading trigger. Is qmail-send still
running? If so, strace it. What's it doing?
>The only piece I note is that trigger has a file size of 63 before and 0
>afterwards. Is it normal for this pipe to increase/decrease in size, or is
>that normal behaviour for a pipe?
That's normal pipe behaviour, but it's not normal for qmail-send to
not read bytes soon after they're written.
-Dave
