On Thu, 2 Mar 2006, Daryl C. W. O'Shea wrote:
Daryl,
Still working on clearing the other issues. I'm using MOST of the plugins
that come with spamassassin, but no third party plugins -- there's some
third party RULESETS including rules du jour, chickenpox, etc -- but those
are all fairly straightforwards, and reasonably well maintained.
There's one minor issue that I'd like to bring to your attention:
And 4) This whenever it gets hung up (those __alarm__ things couldn't be
more vague, could they?):
They're timeouts. Running in debug mode will make it clear where the
timeouts are from.
Mar 2 12:53:07 quark spamd[94770]: __alarm__
Mar 2 12:53:07 quark spamd[94770]: __alarm__
Mar 2 12:53:08 quark spamd[62721]: prefork: child states:
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
Mar 2 12:53:08 quark spamd[62721]: prefork: server reached --max-clients
setting, consider raising it
Mar 2 12:53:08 quark spamd[47482]: spamd: processing message
<[EMAIL PROTECTED]> for spam:58
Mar 2 12:53:09 quark spamd[51067]: child processing timeout at
/usr/local/bin/spamd line 1088, <GEN1808> line 184.
Mar 2 12:53:09 quark spamd[51067]: child processing timeout at
/usr/local/bin/spamd line 1088, <GEN1808> line 184.
Mar 2 12:53:09 quark spamd[94770]: spamd: connection from prime.gushi.org
[65.125.228.130] at port 2352
Mar 2 12:53:13 quark spamd[94757]: __alarm__
Mar 2 12:53:13 quark spamd[94757]: __alarm__
Mar 2 12:53:14 quark spamd[92467]: __alarm__
Mar 2 12:53:14 quark spamd[92467]: __alarm__
Mar 2 12:53:14 quark spamd[62721]: prefork: child states:
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
Mar 2 12:53:14 quark spamd[62721]: prefork: server reached --max-clients
setting, consider raising it
Mar 2 12:53:15 quark spamd[49242]: spamd: processing message
<[EMAIL PROTECTED]> for tylersticka:58
Mar 2 12:53:15 quark spamd[62721]: prefork: child states:
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
Mar 2 12:53:15 quark spamd[62721]: prefork: server reached --max-clients
setting, consider raising it
Mar 2 12:53:16 quark spamd[51061]: child processing timeout at
/usr/local/bin/spamd line 1088, <GEN1801> line 86.
Mar 2 12:53:16 quark spamd[51061]: child processing timeout at
/usr/local/bin/spamd line 1088, <GEN1801> line 86.
Mar 2 12:53:16 quark spamd[51066]: spamd: identified spam (8.2/5.0) for
nomylamm:58 in 314.8 seconds, 1430 bytes.
I don't know if these relate to the original bug enough -- perchance you
can tell me?
I *AM* running in debug mode -- have been for months. My full command
line is as follows:
-D -u spamd -i -A 72.9.101.130,65.125.237.232,65.125.228.130,127.0.0.1 -q
-d -m 40 -r /tmp/spamd.pid -l --min-spare=5 --max-spare=20
I also draw attention to the fact that each PID is __alarm__'ing TWICE.
If all those busy children aren't actually doing anything, then yeah, that's
a problem.
I'd get all your other problems cleared up first though.
Working on it.
-Dan
--
"No mowore webooting!!!"
-Paul, 10-16-99, 10 PM
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---------------------------
