RE: A lot of this going around
Aug 7 18:04:30 d_baron spamd[28549]: bayes: write failed to Bayes journal /home/david/.spamassassin/bayes_journal (0 of 3624)! Getting numerous messages of this form. Things seem to be working normally! (Note that sa-update failed this morning due to problems at the site.) Also these: Aug 7 18:03:38 d_baron spamd[28529]: Exiting eval via last at /usr/share/perl5/Mail/SpamAssassin/BayesStore/DBM.pm line 1127.
Re: A lot of this going around
On Mon, Aug 07, 2006 at 09:28:12PM +0300, David Baron wrote: Aug 7 18:04:30 d_baron spamd[28549]: bayes: write failed to Bayes journal /home/david/.spamassassin/bayes_journal (0 of 3624)! Getting numerous messages of this form. Things seem to be working normally! Aug 7 18:03:38 d_baron spamd[28529]: Exiting eval via last at /usr/share/perl5/Mail/SpamAssassin/BayesStore/DBM.pm line 1127. The latter is caused by the former, btw. Perhaps something is over quota or otherwise out of space? Alternately, something like selinux restricting what spamd can do? The first error happens if you can open the journal file for appending, but doing the write actually fails (in this case, nothing was able to be written to the file). -- Randomly Generated Tagline: The nice thing about Windows is - It does not just crash, it displays a dialog box and lets you press 'OK' first. - Arno Schaefer's .sig pgp2wIMKD1dna.pgp Description: PGP signature
Re: A lot of this going around
On Monday 07 August 2006 21:34, Theo Van Dinter wrote: On Mon, Aug 07, 2006 at 09:28:12PM +0300, David Baron wrote: Aug 7 18:04:30 d_baron spamd[28549]: bayes: write failed to Bayes journal /home/david/.spamassassin/bayes_journal (0 of 3624)! Getting numerous messages of this form. Things seem to be working normally! Aug 7 18:03:38 d_baron spamd[28529]: Exiting eval via last at /usr/share/perl5/Mail/SpamAssassin/BayesStore/DBM.pm line 1127. The latter is caused by the former, btw. Perhaps something is over quota or otherwise out of space? Alternately, something like selinux restricting what spamd can do? The first error happens if you can open the journal file for appending, but doing the write actually fails (in this case, nothing was able to be written to the file). Yup. Some stuff eats up your home partition and does not even tell you. Thanks for the hint.
Re: A lot of these going around
On Thursday 18 May 2006 16:36, Ronald Nsubuga wrote: check the retry time and what os are u running pliz and the version you are using for spamassasin? retries less than 1 minute. Debian Sid, SA 3.1.1
Re: A lot of these going around
On Thursday 18 May 2006 16:36, Ronald Nsubuga wrote: check the retry time and what os are u running pliz and the version you are using for spamassasin? retries less than 1 minute. Debian Sid, SA 3.1.1 Bunch of these error messages seem to happening every few (five?) hours.
Re: A lot of these going around
On Thursday 18 May 2006 22:50, Matt Kettler wrote: David Baron wrote: On Thursday 18 May 2006 20:40, Matt Kettler wrote: David Baron wrote: May 18 11:50:22 d_baron spamc[5797]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused Seems harmless though annoying. Fix? Is spamd running? Of course. Is spamd configured to allow connections from 127.0.0.1? (ie: what are you passing after the -A parameter to spamd?) There is no -A parameter used. 127.0.0.1 is loopback. Do I need it (and why was it not placed on installation)?
RE: A lot of these going around
Or maybe some rejecting connection due to high load messages in je system logs? From: Matt Kettler [mailto:[EMAIL PROTECTED] Sent: Thu 18-May-06 21:50 To: David Baron Cc: users@spamassassin.apache.org Subject: Re: A lot of these going around David Baron wrote: On Thursday 18 May 2006 20:40, Matt Kettler wrote: David Baron wrote: May 18 11:50:22 d_baron spamc[5797]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused Seems harmless though annoying. Fix? Is spamd running? Of course. Is spamd configured to allow connections from 127.0.0.1? (ie: what are you passing after the -A parameter to spamd?)
Re: A lot of these going around
David Baron wrote: May 18 11:50:22 d_baron spamc[5797]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused Seems harmless though annoying. Fix? Is spamd running?
Re: A lot of these going around
On Thursday 18 May 2006 20:40, Matt Kettler wrote: David Baron wrote: May 18 11:50:22 d_baron spamc[5797]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused Seems harmless though annoying. Fix? Is spamd running? Of course.
Re: A lot of these going around
David Baron wrote: On Thursday 18 May 2006 20:40, Matt Kettler wrote: David Baron wrote: May 18 11:50:22 d_baron spamc[5797]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused Seems harmless though annoying. Fix? Is spamd running? Of course. Is spamd configured to allow connections from 127.0.0.1? (ie: what are you passing after the -A parameter to spamd?)
