You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ruleqa@spamassassin.apache.org by Jari Fredriksson <ja...@iki.fi> on 2018/11/06 16:25:30 UTC
Re: Tons of errors in todays masscheck
> Jari Fredriksson <ja...@iki.fi> kirjoitti 30.10.2018 kello 17.15:
>
> I had a kilometre long feedback mail from masscheckworker which ended like this.
>
>
> locker: creating link /home/jarif/masscheckwork/nightly_mass_check/masses/spamassassin/bayes.lock to /home/jarif/masscheckwork/nightly_mass_check/masses/spamassassin/bayes.lock.sa-ruleqa.c.sa-ruleqa.internal.12698 failed: File exists at /home/jarif/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/Locker/UnixNFSSafe.pm line 91.
> locker: creating link /home/jarif/masscheckwork/nightly_mass_check/masses/spamassassin/bayes.lock to /home/jarif/masscheckwork/nightly_mass_check/masses/spamassassin/bayes.lock.sa-ruleqa.c.sa-ruleqa.internal.12694 failed: File exists at /home/jarif/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/Locker/UnixNFSSafe.pm line 91.
> locker: creating link /home/jarif/masscheckwork/nightly_mass_check/masses/spamassassin/bayes.lock to /home/jarif/masscheckwork/nightly_mass_check/masses/spamassassin/bayes.lock.sa-ruleqa.c.sa-ruleqa.internal.12697 failed: File exists at /home/jarif/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/Locker/UnixNFSSafe.pm line 91.
> locker: creating link /home/jarif/masscheckwork/nightly_mass_check/masses/spamassassin/bayes.lock to /home/jarif/masscheckwork/nightly_mass_check/masses/spamassassin/bayes.lock.sa-ruleqa.c.sa-ruleqa.internal.12696 failed: File exists at /home/jarif/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/Locker/UnixNFSSafe.pm line 91.
> 11:09:51 up 1:09, 0 users, load average: 14.76, 14.85, 14.35
> rsync -Pcqz ham-jarif.log spam-jarif.log *munged*/
> 11:10:06 up 1:09, 0 users, load average: 11.64, 14.16, 14.13
>
That went away, but now for some days I have had this:
tons of
Syncing nightly_mass_check
check: dns_block_rule URIBL_BLOCKED hit, creating /dnsblock_multi.uribl.com
check: dns_block_rule URIBL_BLOCKED hit, creating /dnsblock_multi.uribl.com
check: dns_block_rule URIBL_BLOCKED hit, creating /dnsblock_multi.uribl.com
What is that? I have a local dns which does not query some ISP or public name server, but itself resolves. And as far as I know, weekly mass check itself does not even do uribl tests...
My normal mail server operation continues normally, and there is no URIBL_BLOCKED either. I see URIBL_BLOCKED only in masscheck report.
br. jarif
Re: Tons of errors in todays masscheck
Posted by Henrik K <he...@hege.li>.
On Tue, Nov 06, 2018 at 06:25:30PM +0200, Jari Fredriksson wrote:
>
> That went away, but now for some days I have had this:
>
> tons of
>
> Syncing nightly_mass_check
> check: dns_block_rule URIBL_BLOCKED hit, creating /dnsblock_multi.uribl.com
> check: dns_block_rule URIBL_BLOCKED hit, creating /dnsblock_multi.uribl.com
> check: dns_block_rule URIBL_BLOCKED hit, creating /dnsblock_multi.uribl.com
>
> What is that? I have a local dns which does not query some ISP or public name server, but itself resolves. And as far as I know, weekly mass check itself does not even do uribl tests...
>
> My normal mail server operation continues normally, and there is no URIBL_BLOCKED either. I see URIBL_BLOCKED only in masscheck report.
Are you using (latest) automasscheck-minimal.sh?
Where are the lines describing what command is run?
Syncing nightly_mass_check
SVN revision = 1845877
+ /usr/local/perl-sa/bin/perl ./mass-check --hamlog=ham-hege.log --spamlog=spam-hege.log -j 2 --progress --after=-174182400 ham:dir:/data/sa/pristine_ham --after=-4838400 spam:dir:/data/sa/pristine_spam
Indeed it should not be possible to even launch DNS without --net. And I
don't see any way how dns_block_rule could hit unless you are actually
hitting it.