> >> I'll second this, SA 3.1.5 & FuzzyOCR on RHEL-AS4
> >>
> >> I've been seeing this off & on ever since I added FuzzyOCR.
> >> Logs seem to correlate to FuzzyOCR processing a gif image during a
> >> peak of messages. Get FuzzyOcr.log message:
> >> FuzzyOcr received timeout after running "10" seconds.
> >>
> >>
> >
> >I'm running SA 3.1.5 with FuzzyOCR. I'm seeing errors in the FuzzOCR
> >log, like this:
> >
> >
> >[2006-10-18 09:34:24] FuzzyOcr received timeout after running "10"
seconds.
> >[2006-10-18 09:49:14] FuzzyOcr received timeout after running "10"
seconds.
> >[2006-10-18 10:09:26] Unexpected error in pipe to external programs.
> > Please check that all helper programs are installed
> >and in the correct path.
> > (Pipe Command "/usr/bin/gifasm -d
> >/tmp/.spamassassin2589Eye8ALtmp/out", Pipe exit code 1 (""), Temporary
> >file: "/tmp/.spamassassin25893ZSX3Ltmp")
> >
> >
> >But I'm no longer getting children in the K state, since I put a spamd
> >restart into the logrotate script. I haven't turned off FuzzyOCR which
> >is doing an excellent job for me.
> >
> >This isn't particularly conclusive, I'm afraid, because when I was
> >seeing the problem it was sporadic and occasional, so it might just be
> >luck, though it's been OK for a few days.
>
> I've got my timeout here higher at 60 (slower box) and am not seeing
> timeout errors or any K processes with 3.1.5 since switching back. It
> only started with SA 3.1.7 so I'm thinking its something there thats
> causing the issue.
>
> ===[George R. Kasica]=== +1 262 677 0766
> President +1 206 374 6482 FAX
> Netwrx Consulting Inc. Jackson, WI USA
> http://www.netwrx1.com
> [EMAIL PROTECTED]
> ICQ #12862186
>
>
It may be too soon to tell, but so far this seems to be working for me:
- went back to SA 3.1.7
- switched from FuzzyOCR 2.3b to FuzzyOCR 2.3rc1
- commented out the FUZZY_OCR_KNOWN_MD5 rule - the rule was there but all
the options for it were already commented out
Under this configuration spamassassin has been running well again on my
FreeBSD machine. This ran since about 3:00pm yesterday (10-18-06) through
midnight, when some cleanup jobs reverted is back to not using FuzzyOCR. I
put it back in place this morning and it's been running great for about 2
hours now. By the dates on the website it looks like the 2.3rc1 version is
just a little older than the 2.3b, but it's working without the hung
processes.
And I was also getting the "FuzzyOcr received timeout after running "10"
seconds." errors, but am not (yet anyway) under this configuration.
Sandy
