Bug 4407 - spamd error message every 5 minutes prefork: sysread(8) failed after 300 secs ...
Summary: spamd error message every 5 minutes prefork: sysread(8) failed after 300 secs...
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: PC FreeBSD
: P5 normal
Target Milestone: 3.1.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-16 12:56 UTC by Andy Jezierski
Modified: 2005-06-17 06:15 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
spamd debug output text/plain None Andy Jezierski [NoCLA]
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Jezierski 2005-06-16 12:56:37 UTC 
New install, running spamd on FreeBSD 5.4 produces error messages every 5 
minutes. Seemd to run fine though.

startup options: -c -d -u spamd -D -s /var/log/spamd.log -r /var/run/spamd.pid

FreeBSD 5.4
Sendmail 8.13.3

See attached debug.
Comment 1 Andy Jezierski 2005-06-16 13:06:00 UTC 
Created attachment 2943 [details]
spamd debug output

Deleted thousands of duplicate lines from file. Original file was 1.4M.
Comment 2 Justin Mason 2005-06-16 13:38:42 UTC 
ok, this is actually fine.  looking into it, this is what happens if the spamd
receives no requests in 5 minutes.  it's harmless.

however, it is unattractive -- I'll come up with a patch...
Comment 3 Justin Mason 2005-06-16 18:06:14 UTC 
Sending        lib/Mail/SpamAssassin/SpamdForkScaling.pm
Transmitting file data .
Committed revision 191042.


fixed.
Comment 4 Andy Jezierski 2005-06-17 08:23:22 UTC 
Looks like the messages are gone, but running in debug mode, it looks like it 
now times out every 2 1/2 minutes instead of every 5 minutes.  Normal? 
Oversight?

Partial debug output:

Fri Jun 17 10:14:08 2005 [6446] dbg: prefork: periodic ping from spamd parent
Fri Jun 17 10:14:08 2005 [6446] dbg: prefork: sysread(8) not ready, wait max 
300 secs
Fri Jun 17 10:14:08 2005 [6447] dbg: prefork: periodic ping from spamd parent
Fri Jun 17 10:14:08 2005 [6447] dbg: prefork: sysread(9) not ready, wait max 
300 secs
Fri Jun 17 10:16:39 2005 [6446] dbg: prefork: periodic ping from spamd parent
Fri Jun 17 10:16:39 2005 [6446] dbg: prefork: sysread(8) not ready, wait max 
300 secs
Fri Jun 17 10:16:39 2005 [6447] dbg: prefork: periodic ping from spamd parent
Fri Jun 17 10:16:39 2005 [6447] dbg: prefork: sysread(9) not ready, wait max 
300 secs
Fri Jun 17 10:19:10 2005 [6446] dbg: prefork: periodic ping from spamd parent
Fri Jun 17 10:19:10 2005 [6446] dbg: prefork: sysread(8) not ready, wait max 
300 secs
Fri Jun 17 10:19:10 2005 [6447] dbg: prefork: periodic ping from spamd parent
Fri Jun 17 10:19:10 2005 [6447] dbg: prefork: sysread(9) not ready, wait max 
300 secs
Comment 5 Justin Mason 2005-06-17 14:15:52 UTC 
normal -- if it was every 5 minutes, there'd be a race between the timeout code
and the ping code, and sometimes the timeout may win...

we could always make it longer if required, e.g. 4 mins 40 secs.   but I don't
see any problem that'll arise from either.