http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4696
------- Additional Comments From [EMAIL PROTECTED] 2006-01-11 22:55 -------
those logs are a little odd.
spamd-maillog:
Jan 10 23:05:07 eagle spamd[24378]: spamd: server successfully spawned child pro
cess, pid 26130
spamd-trace2:
24378 23:04:49 fork() = 26130
26130 23:04:49 getpid() = 26130
26130 23:04:50 open("/etc/passwd", O_RDONLY) = 15
Is the maillog from a different machine, with clock skew between the two?
otherwise I can't see how it took syslogd 17 seconds to syslog that message.
however -- It *could* be something to do with a slow/remote syslogd slowing up
logging, or extremely heavy load. I notice this in spamd-trace2...
26130 23:04:50 write(4, "<23>spamd[26130]: prefork: sysre"..., 69 <unfinished
...>
26130 23:04:52 <... write resumed> ) = 69
in other words it took 2 seconds just for the syslogd write() call to complete.
that's a *long* time for logging!
actually, looking further into the strace it looks increasingly like load.
e.g.
26130 23:05:04 accept(5, {sin_family=AF_INET, sin_port=htons(45076),
sin_addr=inet_a
ddr("127.0.0.1")}}, [16]) = 13
26130 23:05:04 write(14, "B\0\0f\22\n", 6) = 6
26130 23:05:07 read(13, " 1 Office Pro 2003 \n 2 Adobe Ph"..., 1024) = 1024
26130 23:05:17 read(13, "height=3D23></A> <BR> <BR> <B>Av"..., 1024) = 556
26130 23:05:17 read(13, "height=3D23></A> <BR> <BR> <B>Av"..., 1024) = 556
26130 23:06:25 rt_sigaction(SIGPIPE, {SIG_DFL}, {SIG_IGN}, 8) = 0
now: >1 minute without performing system calls? that's a busy CPU working on
parsing. in general, that scan process carries on as normal, but very slowly;
then:
26130 23:10:07 --- SIGALRM (Alarm clock) ---
So it really is timing out, simply due to extremely high CPU load, it
looks like.
I would look at why it takes 2 seconds to log a syslog message; that's bad.
--j.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
