Package: ddclient Version: 3.7.3-4 Severity: important My smart ISP decided to do some really weird rapid ip changes: Jan 18 14:17:14 dev ddclient[13901]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.173 Jan 18 14:20:39 dev ddclient[21237]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.42 Jan 18 14:25:43 dev ddclient[5889]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.130 Jan 18 14:26:15 dev ddclient[5622]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.42 Jan 18 14:27:15 dev ddclient[13901]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.173 Jan 18 14:30:40 dev ddclient[21237]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.42
This went on and on, soon resulting in: Jan 18 22:26:20 dev ddclient[5889]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.130 Jan 18 22:26:27 dev ddclient[5622]: WARNING: skipping update of my.host.name from xxx.xxx.xxx.130 to xxx.xxx.xxx.42. Jan 18 22:26:27 dev ddclient[5622]: WARNING: last updated Fri Jan 18 22:26:19 2008. Jan 18 22:26:27 dev ddclient[5622]: WARNING: Wait at least 30 seconds between update attempts. Jan 18 22:27:52 dev ddclient[13901]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.173 Jan 18 22:31:14 dev ddclient[21237]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.42 Jan 18 22:36:21 dev ddclient[5889]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.130 Jan 18 22:36:27 dev ddclient[5622]: WARNING: skipping update of my.host.name from xxx.xxx.xxx.130 to xxx.xxx.xxx.42. Jan 18 22:36:27 dev ddclient[5622]: WARNING: last updated Fri Jan 18 22:36:20 2008. Jan 18 22:36:27 dev ddclient[5622]: WARNING: Wait at least 30 seconds between update attempts. Jan 18 22:37:53 dev ddclient[13901]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.173 And later: Jan 19 06:41:51 dev ddclient[5622]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.42 Jan 19 06:41:51 dev ddclient[21237]: WARNING: updating my.host.name: nochg: No update required; unnecessary attempts to change to the current address are considered abusive Jan 19 06:47:23 dev ddclient[5889]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.130 Jan 19 06:48:27 dev ddclient[13901]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.173 Jan 19 06:51:52 dev ddclient[5622]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.42 Jan 19 06:51:52 dev ddclient[21237]: WARNING: updating my.host.name: nochg: No update required; unnecessary attempts to change to the current address are considered abusive Jan 19 06:57:23 dev ddclient[5889]: SUCCESS: updating my.host.name: good: IP address set to xxx.xxx.xxx.130 And finally getting me blocked for abuse. As you can see in the last part, the duplicate updates are simultaneous. When I discovered this, there were *3* ddclient processes running. My guess is the /etc/ppp/ip-up.d/ddclient script spawned a new ddclient process while another one was running, and they kept about doing their business without knowing of eachother. The 3rd process must've been the daemon, which correctly detected the ip went back to its previously known value (skipping update .. ). Maybe it's a bug in ppp that makes the ip-up.d scripts run twice under weird circumstances. Nevertheless, I think multiple ddclients should refuse running for the same interface, or if they are somehow running, they should NOT submit the same information (so i guess this is an upstream bug). Or: another good idea might be to allow for absolutely enforcing the daemon_interval across all ddclients running for the same interface, and make this the default setting. Regards -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable'), (101, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages ddclient depends on: ii debconf [debconf-2.0] 1.5.11etch1 Debian configuration management sy ii initscripts 2.86.ds1-38 Scripts for initializing and shutt ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip ii perl [perl5] 5.8.8-7etch1 Larry Wall's Practical Extraction Versions of packages ddclient recommends: ii libio-socket-ssl-perl 1.01-1 Perl module implementing object or -- debconf information: * ddclient/run_daemon: true * ddclient/interface: ppp0 * ddclient/protocol: dyndns2 * ddclient/run_ipup: true * ddclient/username: ddclient/newconfigfmt: ddclient/modifiedconfig: * ddclient/server: members.dyndns.org * ddclient/daemon_interval: 300 * ddclient/service: www.dyndns.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
