Bob Proulx
2010-May-17 22:42 UTC
[Logcheck-devel] Bug#582060: logcheck-database: bind network unreachable errors
Package: logcheck-database Version: 1.3.8 Severity: normal After double checking that I had the most up to date logcheck-database :-) I am seeing these lines reported. May 17 15:29:33 localhost named[1765]: error (network unreachable) resolving 'software.majix.org/A/IN': 2001:503:ba3e::2:30#53 I believe that this line was intended to match it. ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ named\[[[:digit:]]+\]: ((network|host) (unreachable|down)|connection refused|unexpected RCODE \((FORMERR|SERVFAIL|NXDOMAIN|NOTIMP|REFUSED|YXDOMAIN|YXRRSET|NXRRSET|NOTAUTH|NOTZONE|BADVERS|<rcode [[:digit:]]+>|[[:digit:]]+)\)) resolving '[^[:space:]]+': [.:[:xdigit:]]+#[[:digit:]]+$ The Lenny form of the syslog line would have been: May 17 07:39:43 localhost named[2395]: network unreachable resolving '38.106.104.86.in-addr.arpa/PTR/IN': 2001:610:240:0:53::193#53 The Lenny BIND syslog line matches the rule. Apparently a BIND syslog line format change occurred. I haven't seen enough of the associated errors to know what else may have changed. bind9 1:9.7.0.dfsg.P1-1 For the time being I have added the following as a local rule. ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ named\[[[:digit:]]+\]: error \((network|host) (unreachable|down)\) resolving '[^[:space:]]+': [.:[:xdigit:]]+#[[:digit:]]+$ Thanks! Bob
Debian Bug Tracking System
2010-Jun-04 07:21 UTC
[Logcheck-devel] Bug#582060: marked as done (logcheck-database: bind network unreachable errors)
Your message dated Fri, 04 Jun 2010 07:17:12 +0000 with message-id <E1OKR9U-00066W-Qj at ries.debian.org> and subject line Bug#582060: fixed in logcheck 1.3.9 has caused the Debian Bug report #582060, regarding logcheck-database: bind network unreachable errors to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 582060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582060 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Bob Proulx <bob at proulx.com> Subject: logcheck-database: bind network unreachable errors Date: Mon, 17 May 2010 16:42:59 -0600 Size: 2948 URL: <http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20100604/237aca0e/attachment.eml> -------------- next part -------------- An embedded message was scrubbed... From: Hannes von Haugwitz <hannes at vonhaugwitz.com> Subject: Bug#582060: fixed in logcheck 1.3.9 Date: Fri, 04 Jun 2010 07:17:12 +0000 Size: 6500 URL: <http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20100604/237aca0e/attachment-0001.eml>
Possibly Parallel Threads
- Bug#443908: /etc/logcheck/ignore.d.server/bind: [bind] unexpected RCODE (NOTIMP)
- [PATCH v2v v2 2/2] v2v: Copy static IP address information over for Windows guests (RHBZ#1626503).
- Bug#580260: logcheck-database: dkim-filter needs tweak
- Bug#377276: "Did not receive identification string" warning reappeared
- Bug#444097: /etc/logcheck/ignore.d.server/ddclient: 2 rules to get you started