Cannot find stalled SpamAssassin rule
Arrigo Triulzi
arrigo at alchemistowl.org
Mon Feb 24 18:11:43 CET 2025
OK, $sa_debug = ‘all’ before the “type11” issue:
Feb 24 16:22:22 bagheera amavis[50285]: (50285-01) SA dbg: plugin: Mail::SpamAssassin::Plugin::Bayes=HASH(0x51927fd400) implements 'learner_expire_old_training', priority 0
Feb 24 16:22:22 bagheera amavis[50285]: (50285-01) SA dbg: bayes: expiry starting
Feb 24 16:22:22 bagheera amavis[50285]: (50285-01) SA dbg: locker: refresh_lock: refresh /var/amavisd/.spamassassin/bayes.lock
Feb 24 16:22:22 bagheera amavis[50285]: (50285-01) SA dbg: locker: refresh_lock: refresh /var/amavisd/.spamassassin/bayes.lock
Feb 24 16:22:22 bagheera amavis[50285]: (50285-01) SA dbg: bayes: DB expiry: tokens in DB: 8229942, Expiry max size: 150000, Oldest atime: 1588090802, Newest atime: 1740404443, Last expire: 0, Current time: 1740414142
Feb 24 16:22:22 bagheera amavis[50285]: (50285-01) SA dbg: bayes: expiry check keep size, 0.75 * max: 112500
Feb 24 16:22:22 bagheera amavis[50285]: (50285-01) SA dbg: bayes: token count: 8229942, final goal reduction size: 8117442
Feb 24 16:22:22 bagheera amavis[50285]: (50285-01) SA dbg: bayes: first pass? current: 1740414142, Last: 0, atime: 0, count: 0, newdelta: 0, ratio: 0, period: 43200
Feb 24 16:22:22 bagheera amavis[50285]: (50285-01) SA dbg: bayes: can't use estimation method for expiry, unexpected result, calculating optimal atime delta (first pass)
Feb 24 16:22:22 bagheera amavis[50285]: (50285-01) SA dbg: bayes: expiry max exponent: 9
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) _WARN: bayes: expire_old_tokens: __alarm__ignore__(108/::Plugin::Check::run_eval_tests/1028)
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: bayes: expiry completed
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: bayes: untie-ing
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: bayes: files locked, now unlocking lock
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: locker: safe_unlock: unlink /var/amavisd/.spamassassin/bayes.lock
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: check: tagrun - tag BAYESTCHAMMY is now ready, value: 47
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: check: tagrun - tag BAYESTCSPAMMY is now ready, value: 21
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: check: tagrun - tag BAYESTCLEARNED is now ready, value: 140
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: check: tagrun - tag BAYESTC is now ready, value: 221
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: check: tagrun - tag HAMMYTOKENS is now ready, value: CODE(0x51dd95e628)
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: check: tagrun - tag SPAMMYTOKENS is now ready, value: CODE(0x518efcf808)
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: check: tagrun - tag TOKENSUMMARY is now ready, value: CODE(0x5147547c10)
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: rules: ran eval rule BAYES_05 ======> got hit (1)
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA info: check: exceeded time limit in Mail::SpamAssassin::Plugin::Check::_eval_tests_type11_prineg90_set3, skipping further tests
Feb 24 16:27:16 bagheera amavis[50285]: (50285-01) SA dbg: async: select found 0 responses ready (t.o.=0.0), did 0 callbacks
I don’t see anything obvious…
More information about the amavis-users
mailing list