You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2017/08/26 14:07:48 UTC
[Bug 7464] New: dbg: dns: query failed:
1.4.3.updates.spamassassin.org => SERVFAIL
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7464
Bug ID: 7464
Summary: dbg: dns: query failed: 1.4.3.updates.spamassassin.org
=> SERVFAIL
Product: Spamassassin
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: sa-update
Assignee: dev@spamassassin.apache.org
Reporter: toralf.foerster@gmx.de
Target Milestone: Undefined
t44 sa-update-keys # sa-update -D
Aug 26 16:03:16.136 [2003] dbg: logger: adding facilities: all
Aug 26 16:03:16.136 [2003] dbg: logger: logging level is DBG
Aug 26 16:03:16.136 [2003] dbg: generic: SpamAssassin version 3.4.1
Aug 26 16:03:16.137 [2003] dbg: generic: Perl 5.024001, PREFIX=/usr,
DEF_RULES_DIR=/usr/share/spamassassin, LOCAL_RULES_DIR=/etc/mail/spamassassin,
LOCAL_STATE_DIR=/var/lib/spamassassin
Aug 26 16:03:16.137 [2003] dbg: config: timing enabled
Aug 26 16:03:16.138 [2003] dbg: config: score set 0 chosen.
Aug 26 16:03:16.143 [2003] dbg: generic: sa-update version svn1652181
Aug 26 16:03:16.143 [2003] dbg: generic: using update directory:
/var/lib/spamassassin/3.004001
Aug 26 16:03:16.206 [2003] dbg: diag: perl platform: 5.024001 linux
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Digest::SHA1,
version 2.13
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: HTML::Parser,
version 3.71
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Net::DNS, version
1.1
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: NetAddr::IP,
version 4.078
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Time::HiRes,
version 1.9733
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Archive::Tar,
version 2.04_01
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: IO::Zlib, version
1.10
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Digest::SHA1,
version 2.13
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: MIME::Base64,
version 3.15
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: DB_File, version
1.835
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Net::SMTP,
version 3.08_01
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Mail::SPF,
version v2.009
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Geo::IP, version
1.45
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Net::CIDR::Lite,
version 0.21
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module not installed:
Razor2::Client::Agent ('require' failed)
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: IO::Socket::IP,
version 0.37
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed:
IO::Socket::INET6, version 2.72
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: IO::Socket::SSL,
version 2.024
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Compress::Zlib,
version 2.069001
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Mail::DKIM,
version 0.4
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module not installed: DBI
('require' failed)
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Getopt::Long,
version 2.48
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: LWP::UserAgent,
version 6.15
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: HTTP::Date,
version 6.02
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed:
Encode::Detect::Detector, version 1.01
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed: Net::Patricia,
version 1.22
Aug 26 16:03:16.206 [2003] dbg: diag: [...] module installed:
Net::DNS::Nameserver, version 1558
Aug 26 16:03:16.207 [2003] dbg: gpg: Searching for 'gpg'
Aug 26 16:03:16.207 [2003] dbg: util: current PATH is:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/5.4.0:/home/tfoerste/workspace/bin
Aug 26 16:03:16.207 [2003] dbg: util: executable for gpg was found at
/usr/bin/gpg
Aug 26 16:03:16.207 [2003] dbg: gpg: found /usr/bin/gpg
Aug 26 16:03:16.207 [2003] dbg: gpg: release trusted key id list:
5E541DC959CB8BAC7C78DFDC4056A61A5244EC45
0C2B1D7175B852C64B3CDC716C55397824F434CE
Aug 26 16:03:16.208 [2003] dbg: util: secure_tmpfile created a temporary file
/tmp/.spamassassin2003YzVGwltmp
Aug 26 16:03:16.208 [2003] dbg: channel: attempting channel
updates.spamassassin.org
Aug 26 16:03:16.208 [2003] dbg: channel: using existing directory
/var/lib/spamassassin/3.004001/updates_spamassassin_org
Aug 26 16:03:16.208 [2003] dbg: channel: channel cf file
/var/lib/spamassassin/3.004001/updates_spamassassin_org.cf
Aug 26 16:03:16.208 [2003] dbg: channel: channel pre file
/var/lib/spamassassin/3.004001/updates_spamassassin_org.pre
Aug 26 16:03:16.208 [2003] dbg: channel: metadata version = 1799552, from file
/var/lib/spamassassin/3.004001/updates_spamassassin_org.cf
Aug 26 16:03:16.251 [2003] dbg: dns: query failed:
1.4.3.updates.spamassassin.org => SERVFAIL
Aug 26 16:03:16.256 [2003] dbg: dns: query failed:
mirrors.updates.spamassassin.org => SERVFAIL
channel: no 'mirrors.updates.spamassassin.org' record found, channel failed
Aug 26 16:03:16.256 [2003] dbg: diag: updates complete, exiting with code 4
Happened at a stable Gentoo with 3.4.1-r8
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7464] dbg: dns: query failed: 1.4.3.updates.spamassassin.org =>
SERVFAIL
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7464
Toralf Förster <to...@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |toralf.foerster@gmx.de
--- Comment #2 from Toralf Förster <to...@gmx.de> ---
Well, I can continue this on the mailing list.
FWIW this issue happens b/c I do use dnsmasq and have set
"dnssec-check-unsigned" in the conf file. Just activating "dnssec" itself let
sa-update works, but both options together let sa-update fail.
Because I did not changed anything at my DNS for a longer time I'd assume that
the issue is triggered by something else outside ?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7464] dbg: dns: query failed: 1.4.3.updates.spamassassin.org =>
SERVFAIL
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7464
Bill Cole <sa...@billmail.scconsult.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sa-bugz-20080315@billmail.s
| |cconsult.com
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #1 from Bill Cole <sa...@billmail.scconsult.com> ---
(In reply to Toralf Förster from comment #0)
> Aug 26 16:03:16.251 [2003] dbg: dns: query failed:
> 1.4.3.updates.spamassassin.org => SERVFAIL
> Aug 26 16:03:16.256 [2003] dbg: dns: query failed:
> mirrors.updates.spamassassin.org => SERVFAIL
> channel: no 'mirrors.updates.spamassassin.org' record found, channel failed
> Aug 26 16:03:16.256 [2003] dbg: diag: updates complete, exiting with code 4
I cannot reproduce this.
I have tried sa-update and dig to test the TXT & SOA records for
mirrors.updates.spamassassin.org and 1.4.3.updates.spamassassin.org (which is
resolved via a CNAME pointing to 3.3.3. updates.spamassassin.org.) With dig I
tried all of these resolution paths: my own recursing resolver, Google and
Level3 public resolvers, and each of the authoritative nameservers for the
zone. All are providing identical correct answers and the same SOA serial
number for the zone.
SERVFAIL DNS responses can result from a wide range of different errors at any
point in the chain of nameservers between your local resolver and the
authoritative nameservers for the name being resolved. Having tested 8
resolution paths and finding no issues, the possibilities remaining are:
1. The issue was transient and has been resolved on its own.
2. The issue is specific to your particular DNS resolution path, and so in no
sense a bug in SpamAssassin.
For future reference, this sort of problem which is not likely to be within the
SpamAssassin code itself but instead most likely rooted in external services is
better addressed to the spamassassin-users mailing list, which has a much
larger audience of fellow sysadmins who may be able to corroborate the problem
and/or diagnose it.
--
You are receiving this mail because:
You are the assignee for the bug.