Hmmm, I'd seen this problem before. So I logged into my server, but no hung ddclient processes:
% ps auxwww | grep ddclient
%
Hmmm, poking around some more, looks like the problem maybe fixed itself?
%grep ddclient /var/log/daemon.log
May 25 08:21:48 casey ddclient[13892]: WARNING: forcing update of Home from 98.222.63.70 to 98.222.63.70; 30 days since last update on Fri Apr 24 21:31:51 2009.
May 25 08:21:48 casey ddclient[13892]: WARNING: forcing update of vwelch.dyndns.org from 98.222.63.70 to 98.222.63.70; 30 days since last update on Fri Apr 24 21:31:51 2009.
May 25 08:21:50 casey ddclient[13892]: SUCCESS: updating Home: good: IP address set to 98.222.63.70
May 25 08:21:50 casey ddclient[13892]: SUCCESS: updating vwelch.dyndns.org: good: IP address set to 98.222.63.70
Sure enough, logging into DynDNS showed a last update time from this morning.
So apparently there is a race condition between the email warning and the ddclient forcing a refresh.
No comments:
Post a Comment