Hi Vincent,
> Are you running spamd/spamc as root? it is not recommended to run spamd
> as root.
I know, but so far I was too lazy setting it up to run as a user.
There are still some issues, e.g. when I start spamd with
use_auto_whitelist 1
and there is no file auto-whitelist yet, it is
> If you remember my log file, there were a bunch of days in a row with one
> to three of them, then three on April 8th, one on April 9th and none
> since then.
Well, it still could be some kind of watchdog that kills processes when
they use too much CPU or memory. That wouldn't happen on a regula
--- Andy Spiegl <[EMAIL PROTECTED]> wrote:
> Hi Jason,
>
> I found the cause: my stupidess DOH!
>
> I've got a cronjob that kills processes which have been hanging
> around for
> too long. Two days ago I reconfigured it and made a mistake which
> lead to
> exactly this: spamd with etime of mo
It doesn't seem excessive to me, though my whitelist is actually twice
this size. Here's my blacklist from local.cf:
blacklist_from *reunion.com [EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
blacklist_from *rm05.net *adm02.com [EMAIL PROTECTED]
[EMAIL PROTECTED] *agava.ne
Hi Jason,
I found the cause: my stupidess DOH!
I've got a cronjob that kills processes which have been hanging around for
too long. Two days ago I reconfigured it and made a mistake which lead to
exactly this: spamd with etime of more than 60 minutes are killed with
SIGTERM. This cronjob is re
--- Duane Hill <[EMAIL PROTECTED]> wrote:
> On Fri, 13 Apr 2007, J. wrote:
>
> > --- Andy Spiegl <[EMAIL PROTECTED]> wrote:
> >
> >> I seem to have the same problem!
> >>
> >> Yesterday I upgraded from 3.0 to 3.1
> >> (to be exact: 3.0.3-2sarge1 to 3.1.7-1~bpo.1 from Debian
> backports)
> >> an
J. wrote:
I got an obvious spam a little while ago that got scored
"X-Spam-Status: No, hits=? required=?" so I looked up the message in
the system log. Check out line 5 below (server killed by SIGTERM):
I had a similar issue caused by using a very large blacklist; I took out
the blacklist a
pr 13 11:11:03 2007 [1830] info: spamd: processing message
> <[EMAIL PROTECTED]> for
> root:0
> Fri Apr 13 11:11:03 2007 [1830] error: Can't locate
> Sys/Hostname/Long.pm in @INC (@INC contains: lib ../lib
> /usr/share/perl5 /etc/perl /usr/local/lib/perl/5.8.4
> /usr/lo
Fri Apr 13 10:00:02 2007 [20395] info: prefork: child states: II
Fri Apr 13 10:00:09 2007 [20395] info: spamd: server killed by SIGTERM,
shutting down
--
Fri Apr 13 11:11:03 2007 [1830] info: spamd: processing message <[EMAIL
PROTECTED]> for root:0
Fri Apr 13 11:11:03 2007 [1830] error: Ca
On Fri, 13 Apr 2007, J. wrote:
--- Andy Spiegl <[EMAIL PROTECTED]> wrote:
I seem to have the same problem!
Yesterday I upgraded from 3.0 to 3.1
(to be exact: 3.0.3-2sarge1 to 3.1.7-1~bpo.1 from Debian backports)
and now ALL spamds terminate after a while. And I have no clue why!
The worst
Apr 13 10:00:02 2007 [20395] info: prefork: child states: II
Fri Apr 13 10:00:09 2007 [20395] info: spamd: server killed by SIGTERM,
shutting down
--
Fri Apr 13 11:11:03 2007 [1830] info: spamd: processing message <[EMAIL
PROTECTED]> for root:0
Fri Apr 13 11:11:03 2007 [1830] error: Can't
var/log/spamd.log
> Fri Apr 13 00:12:25 2007 [26466] info: spamd: server killed by
> SIGTERM, shutting down
> Fri Apr 13 01:22:06 2007 [26831] info: spamd: server killed by
> SIGTERM, shutting down
> Fri Apr 13 02:00:08 2007 [19154] info: spamd: server killed by
> SIGTERM, shutting down
&g
only Jason and me seem to have this problem
Grateful for any hint!
Andy.
gold.akte.de:~#grep "server killed by SIGTERM" /var/log/spamd.log
Fri Apr 13 00:12:25 2007 [26466] info: spamd: server killed by SIGTERM,
shutting down
Fri Apr 13 01:22:06 2007 [26831] info: spamd: server killed
tates: II
Apr 9 10:35:10 localhost spamd[8657]: spamd: connection from
binaryops.com [127.0.0.1] at port 54468
Apr 9 10:35:10 localhost spamd[8657]: spamd: checking message
<[EMAIL PROTECTED]> for qscand:210
Apr 9 10:35:10 localhost spamd[25816]: spamd: server killed by
SIGTERM, shuttin
14 matches
Mail list logo
