At 11:03 PM 12/23/00 +0100, you wrote:
>Hi there,
>
>I am sorry to bug you again with this but I still can't get it fixed. The
>multipart completion is giving me a lot of headache. When the multipart
>completion system is turned on, it drops a lot of messages:
>
>Parts 5489:485 2335mb, In 1651467 686551mb, Complete 108632 42066mb, 7%
>6%, Rej 4%
>Drop 614666mb, Err 221 Rotated 35 minutes ago, Upto 30 0.27 35
>
>Look at the drops: 614 GB!!! And only 42 GB got completed. I am running
>5.4j7 btw.
>
>When I turn the sytem off, most of the multiparts get through, but they
>are not completed. In fact, 99% of all multipart messages are not
>complete. I have made sure that the feed we get is complete and I also
>made sure that the system has enough performance. It all looks right. But
>it is still dropping so much multiparts. What does it actually mean when
>things get dropped? Why are they dropped?
They are dropped if the multi part buffer runs out of space before all the
parts
of that particular message have arrived. So there are in theory only 4
explanations
1) The incoming feed is not complete
2) The system is not fast enough when the multi part buffer is
turned on
3) The multi part buffer is too small
4) Something else :-)
It sounds to me like '3' is the most likey candidate at the moment, so if you
have the space increase the multi part buffer size.
Second you have a 4% rejection figure, examine dnews.in or parterr.log to
see why those parts are being rejected it may be you need to modify a spam rule
or something.
Lastly do you have thread_in true ? If not I'd add that.
Let us know if none of that helps and send the status and stats output to
show what it records after a few hours.
>BTW: This is a Cidera feed, and it is the only feed we have. Does anyone
>have experience with this particular newsfeed provider?
Yes we have several customers using it and it seems to be pretty good
from what I've seen but it is 'big'.
ChrisP.
