Logcheck devel - Sep 2007 - Bug#444097: /etc/logcheck/ignore.d.server/ddclient: 2 rules to get you started

Package: logcheck
Version: 1.2.62
Severity: wishlist

Here are two rules for ddclient, a client for dynamic IP services such
as DynDNS or DynIP:

  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ddclient\[[[:digit:]]+\]: SUCCESS: 
updating [._[:alnum:]-]+: good: IP address set to [:[:xdigit:].]+$
  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ddclient\[[[:digit:]]+\]: WARNING:  forcing
update of [._[:alnum:]-]+ from [:[:xdigit:].]+ to [:[:xdigit:].]+; [[:digit:]]+
days since last update on \w{3} \w{3} [ :0-9]{16}\.$


Looking at the code, the first rule should match most (though not all)
services.  It's more or less impossible to say for sure, though -- who's
to say that all services return "good" upon success, for example.  All
I
can say is that it works for me and my static DynDNS address.  (Let the
other users file their own bug reports.  <g>)

As for the second rule, despite being issued as a warning, it's
perfectly normal for static DynDNS hosts, and will appear once a month
if your address doesn't change.  (Basically, DynDNS prohibits updating
with the same IP over and over, but will allow such an update after 28
days, as their record expires after 35 days.  ddclient thus forces an
update after 30 days to be safe.)

BTW, I filed this report under the server level, as it is quite
conceivable to have a (small) server running behind a dynamic IP, for
example as a router.  (I myself am maintaining two such machines.)


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-k7 (SMP w/1 CPU core)
Locale: LANG=en_CA.utf-8, LC_CTYPE=en_CA.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages logcheck depends on:
ii  adduser          3.105                   add and remove users and groups
ii  cron             3.0pl1-100              management of regular background p
ii  lockfile-progs   0.1.11                  Programs for locking and unlocking
ii  logtail          1.2.62                  Print log file lines that have not
ii  mailx            1:8.1.2-0.20070424cvs-1 A simple mail user agent
ii  postfix [mail-tr 2.4.5-4                 High-performance mail transport ag
ii  sysklogd [system 1.5-1                   System Logging Daemon

Versions of packages logcheck recommends:
ii  logcheck-database             1.2.62     database of system log rules for t

-- no debconf information

Your message dated Tue, 03 Jun 2008 22:47:04 +0000
with message-id <E1K3fHU-0000MD-CA at ries.debian.org>
and subject line Bug#444097: fixed in logcheck 1.2.64
has caused the Debian Bug report #444097,
regarding /etc/logcheck/ignore.d.server/ddclient: 2 rules to get you started
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.)


-- 
444097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444097
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: =?utf-8?b?RnLDqWTDqXJpYyBCcmnDqHJl?= <fbriere at fbriere.net>
Subject: /etc/logcheck/ignore.d.server/ddclient: 2 rules to get you started
Date: Tue, 25 Sep 2007 23:13:22 -0400
Size: 3873
Url:
http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20080603/d3b6e034/attachment.eml
-------------- next part --------------
An embedded message was scrubbed...
From: maximilian attems <maks at debian.org>
Subject: Bug#444097: fixed in logcheck 1.2.64
Date: Tue, 03 Jun 2008 22:47:04 +0000
Size: 9508
Url:
http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20080603/d3b6e034/attachment-0001.eml