http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5007
Summary: Frequent "sysread not ready"-messages
Product: Spamassassin
Version: 3.1.3
Platform: Other
URL: http://www.mail-
archive.com/[email protected]/msg28286.html
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: spamc/spamd
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
There is a problem that has been mighty annoying for a while. The main symptoms
that I see is that SA does not return a result at all, just
X-Spam-Status: No, hits= required=
tests=
Looking more carefully into it with debugging on, I see a lot of messages like
Jul 9 12:38:03 robin spamd[10366]: prefork: sysread(9) not ready, wait
max 300 secs
and I believe that is connected to the problem.
It does not occur with 100% reproducability, but I do see it several times a
day.
My setup is that I have spamd 3.1.3 on a machine on its own backed by a Pg 8.1
bayesstore on a Debian box, mostly sarge, but some upgraded packages where
needed. spamd is called by qpsmtpd 0.32 with remote-spamd capability.
The full calling line for spamd is
/usr/sbin/spamd --ip-address --allowed-ips=192.168.2.0/24 --username spamd --
create-prefs --max-children 5 --helper-home-dir /var/opt/spamd -d --pidfile=/
var/opt/spamd/pid
I posted some time ago a looong message to the users list,
http://www.mail-archive.com/[email protected]/msg28286.html
and most of what I currently have is in that post, so please see the details of
that post. I figured it is better to reference it by URI than attach it.
In a follow-up Daryl pointed to bug #4590. However, my problem differs in that
my system doesn't have high load, and I cannot see any complaints about
syswrite in the logs, only sysread. Thus, I'm taking the chance to submit a new
bug.
Since it happens relatively frequently, I can try to get an strace and similar
if required, but I don't do that routinely, so a little hand-holding would be
appreciated. I'll hang out on IRC when I'm at home, that's often a good forum
to do things like that. :-)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
