You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2005/06/16 21:56:38 UTC

[Bug 4407] New: spamd error message every 5 minutes prefork: sysread(8) failed after 300 secs ...

http://bugzilla.spamassassin.org/show_bug.cgi?id=4407

           Summary: spamd error message every 5 minutes prefork: sysread(8)
                    failed after 300 secs ...
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: normal
          Priority: P5
         Component: spamc/spamd
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: ajezierski@stepan.com


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.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4407] spamd error message every 5 minutes prefork: sysread(8) failed after 300 secs ...

Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4407





------- Additional Comments From ajezierski@stepan.com  2005-06-16 13:06 -------
Created an attachment (id=2943)
 --> (http://bugzilla.spamassassin.org/attachment.cgi?id=2943&action=view)
spamd debug output

Deleted thousands of duplicate lines from file. Original file was 1.4M.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4407] spamd error message every 5 minutes prefork: sysread(8) failed after 300 secs ...

Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4407


kristopher.austin@oc.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kristopher.austin@oc.edu






------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4407] spamd error message every 5 minutes prefork: sysread(8) failed after 300 secs ...

Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4407





------- Additional Comments From ajezierski@stepan.com  2005-06-17 08:23 -------
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






------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4407] spamd error message every 5 minutes prefork: sysread(8) failed after 300 secs ...

Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4407


jm@jmason.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From jm@jmason.org  2005-06-16 18:06 -------
Sending        lib/Mail/SpamAssassin/SpamdForkScaling.pm
Transmitting file data .
Committed revision 191042.


fixed.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4407] spamd error message every 5 minutes prefork: sysread(8) failed after 300 secs ...

Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4407


jm@jmason.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
   Target Milestone|Undefined                   |3.1.0




------- Additional Comments From jm@jmason.org  2005-06-16 13:38 -------
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...



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4407] spamd error message every 5 minutes prefork: sysread(8) failed after 300 secs ...

Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4407





------- Additional Comments From jm@jmason.org  2005-06-17 14:15 -------
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.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.