On Sat, 2010-09-04 at 17:55 -0700, John Hardin wrote: > On Sat, 4 Sep 2010, Chris wrote: > > > On Sat, 2010-09-04 at 14:33 -0700, John Hardin wrote: > >> On Sat, 4 Sep 2010, Chris wrote: > >> > >>> I'm trying to figure out why I'm having ridiculous scan times such as > >>> the above examples. Lower scan times such as in the 20 second range are > >>> the exception rather than the rule. I'm running bind as a local caching > >>> nameserver and it seems to be working correctly. I've just seen a ham > >>> that has a scantime=172.2. Could there be something else on the system > >>> that is affecting this? > >>> > >>> Any advice as to troubleshooting would be appreciated. > >> > >> What version of SA, and are you current on updates (have you run sa-update > >> recently)? > >> > >> Would it be possible to post an example message that exhibits the problem? > > > > Hi John, version is 3.3.0 and updates was last run at 5:11pm. Here is a > > link to a spam that took 302s to process http://ez-files.net/445403 > > Thanks. > > ClamAV took almost a minute and a half to scan that message. > > All of the steps seem slow. I'd suggest that it isn't any particular bad > rule, so much as the system appears overloaded. > > > Awhile ago I logged out and logged back in again, I no longer am seeing > > the above and scan times have decreased considerably, > > ham - scantime=5.7 > > and for a spam that just came in > > scantime=1.6 > > > > Things seem back to normal, for now, though I'm not sure how long > > they'll last. Any idea what could be causing the above? > > That's odd. Are you running in an X session or character? Was there some > other process bogging the system or taking up lots of memory such that it > was swapping, which got killed when you logged out? >
Running an X session, and I noticed that this is back: Sep 4 21:03:50 localhost spamd[8668]: spamd: server successfully spawned child process, pid 8761 Sep 4 21:03:50 localhost spamd[8668]: prefork: child 8761: entering state 0 Sep 4 21:03:50 localhost spamd[8668]: prefork: new lowest idle kid: none Sep 4 21:03:50 localhost spamd[8761]: prefork: sysread(8) not ready, wait max 300 secs Sep 4 21:03:50 localhost spamd[8668]: spamd: server successfully spawned child process, pid 8766 Sep 4 21:03:50 localhost spamd[8668]: prefork: child 8766: entering state 0 Sep 4 21:03:50 localhost spamd[8668]: prefork: new lowest idle kid: none Sep 4 21:03:50 localhost spamd[8766]: prefork: sysread(9) not ready, wait max 300 secs Sep 4 21:03:50 localhost spamd[8668]: prefork: child 8761: entering state 1 Sep 4 21:03:50 localhost spamd[8668]: prefork: new lowest idle kid: 8761 Sep 4 21:03:50 localhost spamd[8668]: prefork: child reports idle Sep 4 21:03:50 localhost spamd[8668]: prefork: child states: IS I've logged out and in again and restarted SA so the above is from running 'service spamassassin restart'. Just what is the sysread(#) not ready error mean? -- Chris KeyID 0xE372A7DA98E6705C
signature.asc
Description: This is a digitally signed message part
