Your message dated Sun, 02 Sep 2007 21:32:38 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Already fixed..
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ddclient
Version: 3.6.7-2
Severity: normal
Due to a botched line in my /etc/udev/rules.d/010_local.rules file that caused
my ethernet interface not to get renamed as expected, I ran into a small bug in
ddclient. Apparently, ddclient looks up the IP address of the update host only
at package startup time, and as a result of my earlier problem, this failed,
leading to the following entries in /var/log/daemon.
May 23 20:04:35 wallace ddclient[4403]: WARNING: cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 23 20:09:35 wallace ddclient[4403]: WARNING: cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 23 20:14:35 wallace ddclient[4403]: WARNING: cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
When I discovered and fixed the problem with my udev rule and got my
'forcedeth' interface working correctly, I continued to get the warnings from
ddclient:
May 23 20:18:53 wallace avahi-daemon[4348]: New relevant interface
forcedeth.IPv4 for mDNS.
May 23 20:18:53 wallace avahi-daemon[4348]: Joining mDNS multicast group
on interface forcedeth.IPv4 with address 192.168.2.103.
May 23 20:18:53 wallace avahi-daemon[4348]: Registering new address
record for 192.168.2.103 on forcedeth.
May 23 20:19:35 wallace ddclient[4403]: WARNING: cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 23 20:24:35 wallace ddclient[4403]: WARNING: cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 23 20:29:35 wallace ddclient[4403]: WARNING: cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
The above warnings were issued even though 'host checkip.dyndns.org' returned
valid IP address lookup. Issuing "/etc/init.d/ddclient restart" cleared the
problem up immediately:
May 23 20:29:54 wallace ddclient[4403]: WARNING: caught SIGTERM;
exiting
May 23 20:29:58 wallace ddclient[7932]: SUCCESS: updating
hostname.dnsalias.org: good: IP address set to aaa.bbb.ccc.ddd
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-amd64-k8-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages ddclient depends on:
ii debconf [debconf-2.0] 1.5.0 Debian configuration management sy
ii perl [perl5] 5.8.8-4 Larry Wall's Practical Extraction
ddclient recommends no packages.
-- debconf information:
* ddclient/run_daemon: true
* ddclient/interface: web
* ddclient/protocol: dyndns2
* ddclient/run_ipup: false
ddclient/newconfigfmt:
ddclient/modifiedconfig:
* ddclient/server: members.dyndns.org
* ddclient/daemon_interval: 300
* ddclient/service: www.dyndns.org
--- End Message ---
--- Begin Message ---
Version: 3.7.3-2
It's now fixed.. Thanks for reporting.
--
Marco Rodrigues
http://Marco.Tondela.org
--- End Message ---
